All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Tom Herbert <therbert@google.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Andrew McGregor <andrewmcgr@gmail.com>,
	Matt Smith <smithm@qca.qualcomm.com>,
	Kevin Hayes <hayes@qca.qualcomm.com>,
	Dave Taht <dave.taht@gmail.com>,
	Derek Smithies <derek@indranet.co.nz>,
	netdev@vger.kernel.org, bloat@bufferbloat.net
Subject: Re: BQL crap and wireless
Date: Wed, 31 Aug 2011 15:48:10 -0400	[thread overview]
Message-ID: <20110831194810.GD2474@tuxdriver.com> (raw)
In-Reply-To: <CAB=NE6VuP=AvYiJsYn_Noc1u0Q=jvQPutHRANdSiLP2v48ogfg@mail.gmail.com>

On Fri, Aug 26, 2011 at 04:27:22PM -0700, Luis R. Rodriguez wrote:
> I've just read this thread:
> 
> http://marc.info/?t=131277868500001&r=1&w=2
> 
> Since its not linux-wireless I'll chime in here. It seems that you are
> trying to write an algorithm that will work for all networking and
> 802.11 devices. For networking is seems tough given driver
> architecture and structure and the hope that all drivers will report
> things in a fairly similar way. For 802.11 it was pointed out how we
> have varying bandwidths and depending on the technology used for
> connection (AP, 802.11s, IBSS) a different number of possible peers
> need to be considered. 802.11 faced similar algorithmic complexities
> with rate control and the way Andrew and Derek resolved this was to
> not assume you could solve this problem and simply test out the water
> by trial and error, that gave birth to the minstrel rate control
> algorithm which Felix later rewrote for mac80211 with 802.11n support
> [1]. Can the BQL algorithm make use of the same trial and error
> mechanism and simply try different values and and use EWMA [2] to pick
> the best size for the queue ?
> 
> [1] http://wireless.kernel.org/en/developers/Documentation/mac80211/RateControl/minstrel
> [2] http://en.wikipedia.org/wiki/Moving_average#Exponential_moving_average
> 
>   Luis

Since Luis has stirred things up, I took the liberty of adding Tom's
BQL series to the debloat-testing tree:

	git://git.infradead.org/debloat-testing.git

I'm not sure how well BQL will interact with my eBDP-inspired hack,
debloat-testing commit d2566a176589775cb3a1de4fade972aa62d551ff
("mac80211: implement eBDP algorithm to fight bufferbloat").  So if
anyone wants to try enabling a wireless driver for BQL, you might
consider reverting that patch or at least testing without it.

<shameless plug>
And, of course, don't forget to come to the Bufferbloat and Networking
track at Linux Plumbers Conference next week in Santa Rosa, CA! :-)
</shameless plug>

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      parent reply	other threads:[~2011-08-31 20:00 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 23:27 BQL crap and wireless Luis R. Rodriguez
2011-08-26 23:27 ` Luis R. Rodriguez
2011-08-29 21:02 ` Luis R. Rodriguez
2011-08-29 21:02   ` Luis R. Rodriguez
2011-08-29 21:10   ` Luis R. Rodriguez
2011-08-29 22:45     ` Dave Taht
2011-08-29 22:54       ` Luis R. Rodriguez
2011-08-29 22:54         ` Luis R. Rodriguez
2011-08-29 23:10         ` Dave Taht
2011-08-29 23:10           ` Dave Taht
2011-08-29 23:15           ` Luis R. Rodriguez
2011-08-29 23:18   ` Andrew McGregor
2011-08-29 23:18     ` Andrew McGregor
2011-08-30  0:24   ` Dave Taht
2011-08-30  1:22     ` Jim Gettys
2011-08-30  1:22       ` Jim Gettys
2011-08-30  1:44       ` Adrian Chadd
2011-08-30  1:48         ` Adrian Chadd
2011-08-30  1:59       ` Andrew McGregor
2011-08-30  1:59         ` Andrew McGregor
2011-08-30  2:12         ` Jim Gettys
2011-08-30  3:34       ` Tom Herbert
2011-08-30  3:42         ` Adrian Chadd
2011-08-30  3:42           ` Adrian Chadd
2011-08-30  4:23           ` Andrew McGregor
2011-08-30  4:23             ` Andrew McGregor
2011-08-30 13:58           ` Jim Gettys
2011-08-30 13:58             ` Jim Gettys
2011-08-30 21:47             ` Andrew McGregor
2011-08-30 21:47               ` Andrew McGregor
2011-08-31 13:28               ` Jim Gettys
2011-08-31 20:50                 ` Luis R. Rodriguez
2011-08-31 20:50                   ` Luis R. Rodriguez
2011-09-01  2:44                   ` Adrian Chadd
2011-09-01 14:13                   ` John W. Linville
2011-09-01 14:13                     ` John W. Linville
2011-09-01 15:08                     ` Jim Gettys
2011-09-01 15:08                       ` Jim Gettys
2011-09-02 22:03                     ` Luis R. Rodriguez
2011-09-02 22:03                       ` Luis R. Rodriguez
     [not found]                   ` <4E5FA74D.5000705@freedesktop.org>
2011-09-02 21:59                     ` Luis R. Rodriguez
2011-09-02 21:59                       ` Luis R. Rodriguez
2011-09-03  3:01                       ` Jim Gettys
2011-09-03  3:01                         ` Jim Gettys
2011-08-30  1:08   ` Dave Taht
2011-08-30  1:08     ` Dave Taht
2011-08-31 19:48 ` John W. Linville [this message]

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=20110831194810.GD2474@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=andrewmcgr@gmail.com \
    --cc=bloat@bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=derek@indranet.co.nz \
    --cc=hayes@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=smithm@qca.qualcomm.com \
    --cc=therbert@google.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 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.