From: Andy Furniss <andyqos@ukfsn.org>
To: Julien Vehent <julien@linuxwall.info>
Cc: "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 15:37:57 +0100 [thread overview]
Message-ID: <4FCA2545.60702@ukfsn.org> (raw)
In-Reply-To: <8063b8e35d17fd072cbdc9908cf12519@njm.linuxwall.info>
Julien Vehent wrote:
> On 2012-06-01 12:42, Niccolò Belli wrote:
>> http://lartc.org is alive and kicking and there is no need for
>> another
>> wiki anymore. I'd like to thank both Bert and Carl-Daniel.
>>
>> Niccolò
>>
>
> Very cool !
> I'll try to find some time and move over some of the content I have
> here:
> http://wiki.linuxwall.info/doku.php/en:ressources:dossiers:networking:traffic_control
A couple of things that stand out after skimming through.
DSL - Jeesper's overhead as noted in the comments is not 5 and anyway I
think his good work has now been superseded by stab as it allows for
negative overheads, which his did not.
man tc-stab has clear and good explanations and examples.
SFQ - well it's literally been years since I knew it in detail, but
limit was (back then at least) for all flows combined.
I tested (maybe not hard enough) quantum < mtu and never managed to
prevent dequeues - I know it's not efficient and "forbiden" but back
then at least it didn't break.
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.
next prev parent reply other threads:[~2012-06-02 14:37 UTC|newest]
Thread overview: 16+ 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
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-02 14:37 ` Andy Furniss [this message]
2012-06-02 14:43 ` Andy Furniss
2012-06-02 15:50 ` Eric Dumazet
2012-06-02 16:58 ` Andy Furniss
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=4FCA2545.60702@ukfsn.org \
--to=andyqos@ukfsn.org \
--cc=darkbasic@linuxsystems.it \
--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 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).