Skip to contentSkip to conversation

netem is broken in 6.18

Bug 220774 Cong Wang 2 participants 2 messages Nov 24, 2025 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]/

A message that is not in the archive (sent off-list or not yet received): [email protected]/

Cong Wang

author
#2 lore raw

---------- Forwarded message ---------
From: <[email protected]>
Date: Fri, Nov 21, 2025 at 3:39 PM
Subject: [Bug 220774] netem is broken in 6.18
To: <[email protected]>

https://bugzilla.kernel.org/show_bug.cgi?id=220774

Gerlinde ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #2 from Gerlinde ([email protected]) ---
You know, in our HA and ECMP setup we sometimes get this strange thing: packets are not lost, but some flows get duplicated for a few hundert milliseconds. Not all flows, only the unlucky ones that get hashed through the broken path. And this makes debugging really a pain, because all metrics say “no loss”, but the application still behave stupid.

So we use netem duplicate on a single mq-queue to copy exactly this situation.

--
You may reply to this email to add a comment.

You are receiving this mail because:
You are on the CC list for the bug.

#3 lore raw

Hi [email protected] (sorry, no name on that email!),

Quoted 16 lines · Cong Wang

---------- Forwarded message ---------
From: <[email protected]>
Date: Fri, Nov 21, 2025 at 3:39 PM
Subject: [Bug 220774] netem is broken in 6.18
To: <[email protected]>

https://bugzilla.kernel.org/show_bug.cgi?id=220774

Gerlinde ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

Quoted 8 lines

--- Comment #2 from Gerlinde ([email protected]) ---
You know, in our HA and ECMP setup we sometimes get this strange thing: packets are not lost, but some flows get duplicated for a few hundert milliseconds. Not all flows, only the unlucky ones that get hashed through the broken path. And this makes debugging really a pain, because all metrics say “no loss”, but the application still behave stupid.

So we use netem duplicate on a single mq-queue to copy exactly this situation.

I may be misunderstanding: You seem to be using a single mq-queue with netem and your requirement seems to be replicating the packet on that single mq-queue? You mention "flow" - how do you map these to the queues?
BTW, you may be aware of this, but you should also be able to mirror arbitrary flows of choice without resorting to using netem. Can you share your config?

cheers,
jamal

Quoted 5 lines

--
You may reply to this email to add a comment.

You are receiving this mail because:
You are on the CC list for the bug.