General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: d@taht.net (Dave Täht)
To: Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Buffer bloat at the sender
Date: Fri, 04 Feb 2011 12:58:31 -0700	[thread overview]
Message-ID: <87vd0zk1w8.fsf@cruithne.co.teklibre.org> (raw)
In-Reply-To: <7ihbcj8w8a.fsf@lanthane.pps.jussieu.fr> (Juliusz Chroboczek's message of "Fri, 04 Feb 2011 19:56:21 +0100")


Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr> writes:

>> I have been looking over the mq qdisc,
>
> Do you understand what it's supposed to do?

The documentation for it is in the Linux tree under 
Documentation/networking/multiqueue.txt

My understanding is that it is a general purpose mechanism to get
traffic into a driver (notably a wireless one) that has multiple queues
implemented, in the hope that classified traffic can then line up with
one of the more appropriate traffic classifications in the 802.11*
standards. [1][2]

It does not seem to be widely used at present, and the example in
the documentation is overgeneralized and does not hint at this use.

There are also all sorts of other interesting hacks^H^H^H^H^H attempts
for a reliable delivery/timeliness compromise in the mac layer in the
802.11 standards, including frame aggregation and the like.

The latest 802.11* draft is now open for review to IEEE members. [3]

How all this stuff interacts in the real world is somewhat undefined.

I'm way too far below this level of the stack to care at present, but
seeing some scripts that actually tried to wedge wireless udp/tcpip
traffic into more appropriate queues at the driver level would be
interesting.


-- 
Dave Taht
http://nex-6.taht.net

[1] http://en.wikipedia.org/wiki/IEEE_802.11e-2005
[2] http://www.intel.com/network/connectivity/resources/doc_library/white_papers/30376201.pdf
[3] http://www.ieee802.org/11/

  reply	other threads:[~2011-02-04 19:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04  9:46 [Bloat] About Stochastic Fair Blue (SFB) Juliusz Chroboczek
2011-02-04 13:56 ` Jim Gettys
2011-02-04 17:33   ` [Bloat] Buffer bloat at the sender [was: About Stochastic Fair Blue (SFB)] Juliusz Chroboczek
2011-02-04 18:24     ` Jim Gettys
2011-02-04 18:58       ` [Bloat] Buffer bloat at the sender Juliusz Chroboczek
2011-02-04 19:26         ` Dave Täht
2011-02-04 18:43     ` Dave Täht
2011-02-04 18:56       ` Juliusz Chroboczek
2011-02-04 19:58         ` Dave Täht [this message]
2011-02-04 20:14           ` Juliusz Chroboczek
2011-02-04 15:12 ` [Bloat] About Stochastic Fair Blue (SFB) Dave Täht
2011-02-04 17:41   ` Juliusz Chroboczek
2011-02-04 18:54     ` Dave Täht
2011-02-04 19:02       ` Juliusz Chroboczek

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vd0zk1w8.fsf@cruithne.co.teklibre.org \
    --to=d@taht.net \
    --cc=Juliusz.Chroboczek@pps.jussieu.fr \
    --cc=bloat@lists.bufferbloat.net \
    /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