From: Stephen Hemminger <shemminger@vyatta.com>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
David Miller <davem@davemloft.net>,
Dave Taht <dave.taht@gmail.com>,
"John A. Sullivan III" <jsullivan@opensourcedevel.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] netem: fix classful handling
Date: Thu, 29 Dec 2011 10:31:49 -0800 [thread overview]
Message-ID: <20111229103149.7256369c@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20111229182502.GD2948@hell>
On Thu, 29 Dec 2011 19:25:03 +0100
Hagen Paul Pfeifer <hagen@jauu.net> wrote:
> * Eric Dumazet | 2011-12-29 19:10:36 [+0100]:
>
> >I dont quite understand the question. The patch I posted is supposed to
> >fix the problem. What do you want to tell to the user ?
>
> I assumed that the patch makes it possible to replace standard tfifo?! Tfifo
> provides strict ordering, other qdisc's do not. So I thought if someone use
> netem rate|jitter with e.g. SFQ then this should be mentioned somewhere. E.g.
> "rate|jitter can only be used with tfifo qdisc". Correct me if I am wrong.
>
> Cheers
This is actually a feature. It is documented that tfifo can be replaced
with pfifo. In other words, if default (tfifo) is used then packets
can be reordered by the delay/jitter values. But if pfifo (or other
qdisc) is used, the packets will not be reordered.
next prev parent reply other threads:[~2011-12-29 18:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 5:12 netem and hierarchical ingress traffic shaping John A. Sullivan III
2011-12-18 19:55 ` Stephen Hemminger
2011-12-19 16:53 ` John A. Sullivan III
2011-12-23 17:33 ` Eric Dumazet
2011-12-23 17:39 ` Eric Dumazet
2011-12-23 17:54 ` Dave Taht
2011-12-23 18:28 ` Eric Dumazet
2011-12-23 18:54 ` Dave Taht
2011-12-23 19:07 ` Stephen Hemminger
2011-12-23 19:21 ` Eric Dumazet
2011-12-29 4:26 ` [PATCH net-next] netem: fix classful handling Eric Dumazet
2011-12-29 6:17 ` Stephen Hemminger
2011-12-29 9:12 ` Eric Dumazet
2011-12-29 16:52 ` Hagen Paul Pfeifer
2011-12-29 17:15 ` Eric Dumazet
2011-12-29 17:43 ` Hagen Paul Pfeifer
2011-12-29 18:10 ` Eric Dumazet
2011-12-29 18:25 ` Hagen Paul Pfeifer
2011-12-29 18:31 ` Stephen Hemminger [this message]
2011-12-29 18:36 ` Eric Dumazet
2011-12-30 22:12 ` David Miller
2011-12-23 19:36 ` netem and hierarchical ingress traffic shaping David Miller
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=20111229103149.7256369c@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hagen@jauu.net \
--cc=jsullivan@opensourcedevel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.