From: Stephen Hemminger <shemminger@linux-foundation.org>
To: netdev@vger.kernel.org
Subject: Re: ESFQ (or SFQ updates) mainline status?
Date: Sat, 19 Jan 2008 20:50:13 -0800 [thread overview]
Message-ID: <20080119205013.61294ad3@deepthought> (raw)
In-Reply-To: <1199474475.3820.65.camel@sally>
On Fri, 04 Jan 2008 11:21:15 -0800
Jeff Gustafson <ncjeffgus@zimage.com> wrote:
> Hi all,
> I have a question about the status of the spiffy updates to SFQ. I
> *really* like the ESFQ idea. I appears to be exactly what I'm looking
> for. From what I can tell from this mailing list, SFQ is getting some
> or all of the ESFQ features. Although the ESFQ web site gives detailed
> information about the status for inclusion in mainline, I am having
> trouble finding out exactly what (if any) parts of ESFQ got into SFQ in
> mainline.
> Did any of the ESFQ-like enhancements for SFQ reach .23 or do I still
> need to patch? I am running a stripped-down Fedora 8 box and it would
> be very convenient if the patches were already in .23 or added by the
> Fedora team.
> I tried to run the ESFQ command against SFQ, but the command was
> rejected:
>
> /sbin/tc qdisc add dev eth1 parent 1:12 handle 12: sfq perturb 10 hash
> ctnatchg
>
> It appears the even if the kernel does have the patches, the shipped
> version tc does not.
>
> ..Jeff
The mainline kernel doesn't have ESFQ, so the distribute version of iproute2
does not. If your distro chooses to add ESFQ to their kernel, then they
need to extend tc as well.
--
Stephen Hemminger <stephen.hemminger@vyatta.com>
prev parent reply other threads:[~2008-01-20 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 19:21 ESFQ (or SFQ updates) mainline status? Jeff Gustafson
2008-01-20 4:50 ` Stephen Hemminger [this message]
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=20080119205013.61294ad3@deepthought \
--to=shemminger@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).