From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Dave Taht <dave.taht@gmail.com>,
"John A. Sullivan III" <jsullivan@opensourcedevel.com>,
netdev@vger.kernel.org
Subject: Re: netem and hierarchical ingress traffic shaping
Date: Fri, 23 Dec 2011 20:21:23 +0100 [thread overview]
Message-ID: <1324668083.2915.15.camel@edumazet-laptop> (raw)
In-Reply-To: <20111223110749.7a690685@nehalam.linuxnetplumber.net>
Le vendredi 23 décembre 2011 à 11:07 -0800, Stephen Hemminger a écrit :
> skb_cb is the dumping ground of the networking layer.
> The assumption was that the qdisc could use the skb_cb
> for it's own scratchpad. Netem is using it for tagging
> packets in the queue.
>
> So basically, netem, choke, and sfb are incompatible with
> each other. This is not that bad, why not add a flag to qdisc
> ops to indicate which qdisc are using cb and block user from
> trying to do something bogus.
This is not how I planned to solve the problem.
I think we need an internal tfifo for netem use.
Then be able to add another qdisc on top of netem.
tfifo as a first stage, hardcoded (only limit is tunable)
[ optional 2nd stage, any qdisc ]
netem_queue()
{
queue packet to tfifo
(eventually at head, of reordering)
}
netem_dequeue()
{
if (other_qdisc) {
for_each_packet_from_tfifo_time_ready() {
other_qdisc->enqueue(skb);
}
try_to_dequeue_one_packet_from(other_qdisc);
} else {
dequeue_one_packet_from_tfifo_time_ready();
}
}
next prev parent reply other threads:[~2011-12-23 19:21 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 [this message]
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
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=1324668083.2915.15.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=dave.taht@gmail.com \
--cc=jsullivan@opensourcedevel.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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