From: Eric Dumazet <eric.dumazet@gmail.com>
To: "John A. Sullivan III" <jsullivan@spiritualoutreach.com>
Cc: netdev@vger.kernel.org
Subject: Re: SFQ on HFSC leaf does not seem to work
Date: Fri, 23 Dec 2011 23:24:23 +0100 [thread overview]
Message-ID: <1324679063.2915.18.camel@edumazet-laptop> (raw)
In-Reply-To: <1324674615.10184.631.camel@denise.theartistscloset.com>
Le vendredi 23 décembre 2011 à 16:10 -0500, John A. Sullivan III a
écrit :
> Should I guess that, from the flood of subsequent emails about patching
> netem that it is not currently possible to do netem and hfsc/sfq on
> ingress traffic using the currently available tools?
>
Yep... current netem is a bit limited.
> It's definitely netem on the ingress. When I run it on egress and
> disable it on ingress, I do not have the problem. But, I see no what of
> getting the netem traffic into or out of SFQ. Thanks - John
>
It'll be possible, after a few patches, but only using net-next, or
waiting a backport to a 3.2 kernel somehow...
next prev parent reply other threads:[~2011-12-23 22:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 6:00 SFQ on HFSC leaf does not seem to work John A. Sullivan III
2011-12-23 6:32 ` Dave Taht
2011-12-23 6:40 ` John A. Sullivan III
2011-12-23 7:08 ` John A. Sullivan III
2011-12-23 8:10 ` Eric Dumazet
2011-12-23 13:13 ` John A. Sullivan III
2011-12-23 13:45 ` Eric Dumazet
2011-12-23 14:00 ` Eric Dumazet
2011-12-23 14:38 ` John A. Sullivan III
2011-12-23 14:59 ` Eric Dumazet
2011-12-23 15:26 ` John A. Sullivan III
2011-12-23 16:16 ` Eric Dumazet
2011-12-23 16:44 ` John A. Sullivan III
2011-12-23 17:06 ` Eric Dumazet
2011-12-23 17:17 ` Eric Dumazet
2011-12-23 17:33 ` John A. Sullivan III
2011-12-23 17:35 ` John A. Sullivan III
2011-12-23 21:10 ` John A. Sullivan III
2011-12-23 22:24 ` Eric Dumazet [this message]
2011-12-23 17:20 ` John A. Sullivan III
2011-12-31 22:17 ` John A. Sullivan III
2011-12-23 15:19 ` [PATCH net-next] sch_hfsc: report backlog information Eric Dumazet
2011-12-23 21:52 ` 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=1324679063.2915.18.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=jsullivan@spiritualoutreach.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