From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ferry Huberts <mailings@hupie.com>
Cc: Johannes Naab <jn@stusta.de>, netdev@vger.kernel.org, hagen@jauu.net
Subject: Re: [PATCH 2/2] net: netem: always adjust now/delay when not reordering
Date: Wed, 21 Aug 2013 10:00:17 -0700 [thread overview]
Message-ID: <1377104417.4226.133.camel@edumazet-glaptop> (raw)
In-Reply-To: <5214E774.8060400@hupie.com>
On Wed, 2013-08-21 at 18:14 +0200, Ferry Huberts wrote:
> Well no. We expected no reordering because reordering is not enabled.
Sending packets with random delays happening in the 'network' _will_
reorder packets at the receiver.
The 'reorder' netem attribute is quite limited and not practical,
because it only queues the packet at the head of the queue instead of
tail. This is not what happens on the networks.
You want something very special, and this needs a new parameter to netem
qdisc, or a new qdisc.
If I setup "netem rate 1Mbit delay 1000ms 50ms", and send a burst of 100
small packets, I expect these _all_ packets reach the destination in
less than 1050ms.
I do not want packet1 being delivered at t0+1020ms,
packet2 being delivered at t0+1020+1030ms
packet100 being delivered at t0+1020+1030++...+ = t0+~100sec
If your patch solves the problem, good, but I see no clear test of this.
next prev parent reply other threads:[~2013-08-21 17:00 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
2013-08-21 16:14 ` Ferry Huberts
2013-08-21 17:00 ` Eric Dumazet [this message]
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=1377104417.4226.133.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=hagen@jauu.net \
--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