From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ferry Huberts <mailings@hupie.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2 2/2] net: netem: always adjust now/delay when not reordering
Date: Wed, 21 Aug 2013 06:30:24 -0700 [thread overview]
Message-ID: <1377091824.4226.102.camel@edumazet-glaptop> (raw)
In-Reply-To: <5214668E.504@hupie.com>
On Wed, 2013-08-21 at 09:04 +0200, Ferry Huberts wrote:
>
> On 21/08/13 08:14, Eric Dumazet wrote:
> > On Wed, 2013-08-21 at 07:59 +0200, 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.
> >>
> >> How to test:
> >> -----------
> >
> > I ask again :
> >
> > Did you test a config with both rate limiting and delay.
>
> (sorry for missing that question)
>
> Just did so and with rate limiting I get no reordering, which is logical
> looking at the code.
>
> The thing is, the evaluation q->rate is within the 'no-reordering' block
> and in the current situation you can get reordering (with that 'strange'
> command). My patch makes sure that no reordering will occur, and
> effectively 'clamps' the realised delay, which currently isn't done.
OK, let me be very clear.
I would like you post the results of regression tests, to make sure that
you do not add a new regression.
It seems that you want _us_ to check all this for you.
With "rate 1Mbits delay 100ms 10ms", and ping probes sent every 100ms,
the pong reply of _all_ probes should be between 90ms and 110ms
Is it still the case after your patch ?
Thanks
next prev parent reply other threads:[~2013-08-21 13:30 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 [this message]
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
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=1377091824.4226.102.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--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