From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: Julien Vehent <julien@linuxwall.info>
Cc: Eric Dumazet <eric.dumazet@gmail.com>, netdev@vger.kernel.org
Subject: Re: [WARNING - VERY LONG] A sysadmin's understanding of HFSC and IFB
Date: Tue, 13 Dec 2011 18:35:31 -0500 [thread overview]
Message-ID: <1323819331.8451.9.camel@denise.theartistscloset.com> (raw)
In-Reply-To: <5f2da864419b2bd2a28c57128df418a6@njm.linuxwall.info>
On Tue, 2011-12-13 at 18:10 -0500, Julien Vehent wrote:
> This is an amazing email and I will definitely sit down and read it
> carefully.
> I've been (silently) following your discussions about HFSC because I've been
> wanting to add a section on HFSC in the TC doc I wrote here:
> http://wiki.linuxwall.info/doku.php/en:ressources:dossiers:networking:traffic_control
>
> The doc I've read so far left me staring at the wall with more questions
> than answers. I'm hoping your text will finally bring a clear view of the
> problem :)
>
> Cheers,
> Julien
>
<snip>
LOL - guess whose web site I have open in my browser as I walk through
experimenting with tc to build a test WAN environment in our lab:
http://wiki.linuxwall.info/doku.php/en:ressources:dossiers:networking:traffic_control
It's wonderfully well done and I've recommended it to several of my
peers. Thanks for putting it together - John
next prev parent reply other threads:[~2011-12-13 23:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 7:17 A sysadmin's understanding of HFSC and IFB John A. Sullivan III
2011-12-09 7:59 ` Eric Dumazet
2011-12-13 23:01 ` [WARNING - VERY LONG] " John A. Sullivan III
2011-12-13 23:10 ` Julien Vehent
2011-12-13 23:35 ` John A. Sullivan III [this message]
2011-12-13 23:42 ` John A. Sullivan III
2011-12-14 5:58 ` John A. Sullivan III
2011-12-14 10:32 ` John A. Sullivan III
2011-12-24 5:20 ` John A. Sullivan III
2011-12-09 8:03 ` Dave Taht
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=1323819331.8451.9.camel@denise.theartistscloset.com \
--to=jsullivan@opensourcedevel.com \
--cc=eric.dumazet@gmail.com \
--cc=julien@linuxwall.info \
--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