From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
babel-users@lists.alioth.debian.org
Subject: Re: [Babel-users] QoS for system critical packets on wireless
Date: Fri, 24 Jun 2011 14:52:28 +0200 [thread overview]
Message-ID: <7iliwrpf1v.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <BANLkTinUbmtKQWdJpOrq5xg0Fnune33pPQ@mail.gmail.com> (Dave Taht's message of "Thu, 23 Jun 2011 09:50:51 -0600")
>> Once you've fought the bloat, there's hopefully no further need to
>> classify these packets.
> As for classification, with asymmetric networks, the canonical example
> of some level needed is moving interactive packets up in priority over
> uploads.
Unless your network is badly underprovisioned, some form of roughly
fair share scheduling (say, SFQ) should be all you need.
> Once you admit there is some need for classication,
I certainly don't. We should be simplifying our networks, not making
them even more complex. (Dave, I'm seriously worried you're heading in
the wrong direction.)
> I admit some fondness for diffserv...
The first step is to admit you have a problem ;-)
-- Juliusz
next prev parent reply other threads:[~2011-06-24 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 15:17 Dave Taht
2011-06-22 22:12 ` [Babel-users] " Juliusz Chroboczek
2011-06-23 15:50 ` Dave Taht
2011-06-24 12:52 ` Juliusz Chroboczek [this message]
2011-06-24 14:07 ` Dave Taht
2011-06-23 2:48 ` Jim Gettys
2011-06-23 3:00 ` Dave Taht
2011-06-23 11:35 ` Jim Gettys
2011-06-23 12:32 ` Dave Taht
2011-06-23 17:23 ` Rick Jones
2011-06-23 18:38 ` Justin McCann
2011-06-26 13:51 ` 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=7iliwrpf1v.fsf@lanthane.pps.jussieu.fr \
--to=jch@pps.jussieu.fr \
--cc=babel-users@lists.alioth.debian.org \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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