From: Eric Dumazet <eric.dumazet@gmail.com>
To: Johannes Naab <jn@stusta.de>
Cc: mailings@hupie.com, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] net: netem: always adjust now/delay when not reordering
Date: Wed, 21 Aug 2013 08:39:35 -0700 [thread overview]
Message-ID: <1377099575.4226.120.camel@edumazet-glaptop> (raw)
In-Reply-To: <5214D9F2.90900@stusta.de>
On Wed, 2013-08-21 at 17:17 +0200, Johannes Naab wrote:
> On 08/20/2013 05:11 PM, Ferry Huberts wrote:
> > From: Ferry Huberts <ferry.huberts@pelagic.nl>
> >
> > Not doing this (current behaviour) introduces reordering.
> >
> > The packet_len_2_sched_time call is the only thing that logically
> > depends on q->rate, so move the now/delay adjustment out of the if.
> >
> > Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
> > ---
>
> Hi,
>
> The documentation for netem does explicitly mention the reordering with
> jitter, and gives instructions on how to avoid it. (I have not tested if
> it works as intended).
Yes.
The user specifically adds a random delay of 0 to 510 ms to packets,
and expect netem to not reorder packets sent every 100ms.
They see netem as a single medium between two endpoints with a guarantee
of no reordering, and cumulative delays.
So if you send a burst of 100 packets, they might expect the last packet
will be send after ~50 seconds.
This clearly needs a new option to netem, because this is not the
default behavior we want.
next prev parent reply other threads:[~2013-08-21 15:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 15:11 [PATCH 1/2] net: netem: do not reorder when reordering is disabled Ferry Huberts
2013-08-20 15:11 ` [PATCH 2/2] net: netem: always adjust now/delay when not reordering Ferry Huberts
2013-08-20 18:31 ` Sergei Shtylyov
2013-08-20 20:33 ` Eric Dumazet
2013-08-21 5:59 ` [PATCH v2 " Ferry Huberts
2013-08-21 6:14 ` Eric Dumazet
2013-08-21 7:04 ` Ferry Huberts
2013-08-21 13:30 ` Eric Dumazet
2013-08-21 14:02 ` mailings
2013-08-21 14:10 ` mailings
2013-08-21 15:17 ` [PATCH " Johannes Naab
2013-08-21 15:39 ` Eric Dumazet [this message]
2013-08-21 16:14 ` Ferry Huberts
2013-08-21 17:00 ` Eric Dumazet
2013-08-21 17:35 ` Stephen Hemminger
2013-08-23 12:50 ` Ferry Huberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1377099575.4226.120.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=jn@stusta.de \
--cc=mailings@hupie.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox