From: Andy Furniss <andyqos@ukfsn.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Julien Vehent" <julien@linuxwall.info>,
"Niccolò Belli" <darkbasic@linuxsystems.it>,
lartc@vger.kernel.org, netfilter@vger.kernel.org,
"Linux Networking Developer Mailing List"
<netdev@vger.kernel.org>
Subject: Re: [Announce] LARTC wiki available
Date: Sat, 02 Jun 2012 17:58:54 +0100 [thread overview]
Message-ID: <4FCA464E.5030002@ukfsn.org> (raw)
In-Reply-To: <1338652231.2760.1706.camel@edumazet-glaptop>
Eric Dumazet wrote:
> On Sat, 2012-06-02 at 15:37 +0100, Andy Furniss wrote:
>
>>
>> Anyway it seems that early this year SFQ got some love and now has
>> several more options (red, headdrop, limit>127, depth as param) - so as
>> long as your iproute/kernel is current have a look at man tc-sfq for
>> details.
>
> Yes, but fq_codel is really better than SFQ.
Ooh, that does look interesting. I hadn't seen that, thanks.
I should really start checking netdev again.
Just pulled iproute git, and see there is a man for codel, but not
fq_codel (yet?).
It would be handy if it/them were added to man tc's "SEE ALSO" section.
next prev parent reply other threads:[~2012-06-02 16:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 15:52 [Announce] LARTC wiki available Niccolò Belli
2011-12-29 0:27 ` Hagen Paul Pfeifer
2011-12-29 9:37 ` Niccolò Belli
2011-12-29 16:19 ` Hagen Paul Pfeifer
2011-12-29 17:13 ` Niccolò Belli
2011-12-29 19:04 ` John A. Sullivan III
2011-12-29 19:04 ` John A. Sullivan III
2012-01-02 12:48 ` Ed W
2012-01-02 13:07 ` Niccolò Belli
2012-06-01 16:42 ` Niccolò Belli
2012-06-01 19:12 ` Julien Vehent
2012-06-01 19:12 ` Julien Vehent
2012-06-02 14:37 ` Andy Furniss
2012-06-02 14:43 ` Andy Furniss
2012-06-02 15:50 ` Eric Dumazet
2012-06-02 16:58 ` Andy Furniss [this message]
2012-06-03 2:36 ` Jesper Dangaard Brouer
2012-06-03 20:05 ` Philip Prindeville
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=4FCA464E.5030002@ukfsn.org \
--to=andyqos@ukfsn.org \
--cc=darkbasic@linuxsystems.it \
--cc=eric.dumazet@gmail.com \
--cc=julien@linuxwall.info \
--cc=lartc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter@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.