From: Dave Taht <dave.taht@gmail.com>
To: "Björn Smedman" <bjorn@openias.org>,
make-wifi-fast@lists.bufferbloat.net
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [Make-wifi-fast] Bayesian rate control
Date: Mon, 24 Oct 2016 08:09:15 -0700 [thread overview]
Message-ID: <CAA93jw6Ec-Nw4GORdBnS10PQFWS4BfooJpZg3J9tD3RKbXAENg@mail.gmail.com> (raw)
In-Reply-To: <CAGp19xcg1qCP3+JNbuiB7Hx=UjLN7KP55wVJT0sKV-iE12501A@mail.gmail.com>
On Sun, Oct 23, 2016 at 6:57 AM, Björn Smedman <bjorn@openias.org> wrote:
> Hi all,
>
> I've been thinking about rate control a bit lately. I've written up
> some of my thoughts in a blog post
> (http://www.openias.org/bayesian-wifi-rate-control), but very briefly
It is nice to see some newer thinking here.
> put I'd like to build a rate control algorithm based on Bayesian
> statistical inference, possibly by modeling the rate control problem
> as a "multi-armed bandit" problem and/or using Thompson sampling.
The paper on minstrel's design was never widely published. I linked to it here:
http://blog.cerowrt.org/post/minstrel/
Looking harder at rate control has long been on my todo list, but at
the top of my list to finish first has been the fair queuing
(fq_codel) and airtime fairness work.
https://blog.tohojo.dk/2016/06/fixing-the-wifi-performance-anomaly-on-ath9k.html#results
http://blog.cerowrt.org/post/real_results
Once you are statistically hitting more stations, more often, on a
more regular basis, with smaller txops, I felt that many things that
were perceived as rate control problems would go away, and other
things become easier.
A basic "fix" to minstrel is to opportunistically sample (which so far
as I know, minstrel-blues does), rather than at a fixed rate.
btw: I called my early (unpublished) attempt at a "minstrel-2", "bard". :)
The now-enormous search space is a big problem in present-day
minstrel, followed by excessive retries/latency when sampling, and
hidden stations are becoming more and more of a problem as densities
go up. (long list of minstrel issues on that first link I posted
above).
> A couple of questions for the list:
>
> 1. Is there anybody else out there thinking along similar lines?
Yes and no. At the moment I am thinking about the insights from the
TCP "BBR" work google just published: (paywalled but at:
http://queue.acm.org/app/ ) where they also point to max-plus algebra
as being helpful for solving the problems it had.
> I'd very much like to find collaborators interested in working on
> this. It coruld serve as a pretty nice masters thesis problem, for
> example.
Please join us over on the make-wifi-fast list. There are more than a
few good papers to be had out of it.
>
> 2. What would be the best hardware/software stack to base this work on?
Presently ath9k is the only game in town, and developing/debugging on
x86 is the easiest.
> I'm thinking the best driver for rate control experimentation would be
> ath9k, right? If so then a TP-Link TL-WA901ND router (apparently based
> on Qualcomm QCA956x SOC) with OpenWrt, and a TP-Link TL-WDN4800 PCIe
> card (apparently based on Atheros AR9380 with PCI ID 168c:0030) for my
> desktop sounds like a good combo, no? But would I have to run a custom
> kernel on my desktop then (or can I somehow get by with an Ubuntu
> standard kernel)?
These days I am using a pcengines apu2 as my primary x86 testbed, with
ath9k and ath10k cards in it (and one day mt72). The new turris omnia
looks like a good platform also. I've been trying to use stuff newer
than AR92xx there.
Another box I really like is the ubnt uap-lite.
Prior to all those, it was the wndr3800, archer c7v2, and nanostation
m5s for outdoor work.
>
> Any other thoughts or pointers are also more than welcome.
>
> Many thanks,
>
> Björn Smedman
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next parent reply other threads:[~2016-10-24 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGp19xcg1qCP3+JNbuiB7Hx=UjLN7KP55wVJT0sKV-iE12501A@mail.gmail.com>
2016-10-24 15:09 ` Dave Taht [this message]
[not found] ` <1477286912.4085.1.camel@sipsolutions.net>
[not found] ` <CAGp19xdgsoyx9Sa=uas1OEiFoJdzFChmt20++9e7fJK=Z1ujWQ@mail.gmail.com>
[not found] ` <1477379678.4390.2.camel@sipsolutions.net>
[not found] ` <CAJ-Vmon0RTAXJMuwANCO23cPsFyFZ17sAHoReuGBG1u1Q9kK6w@mail.gmail.com>
[not found] ` <1477461362.4059.17.camel@sipsolutions.net>
[not found] ` <CAGp19xeDOdF+YuZ34sQrFY+NO4kvzAzuFr0+3Ae62v-a-0eUtg@mail.gmail.com>
2016-10-30 23:37 ` Dave Taht
[not found] ` <A9EF20BC-E559-4537-89F8-5A490C52FD9A@inet.tu-berlin.de>
2017-01-08 17:09 ` [Make-wifi-fast] Fwd: [ath9k-devel] " 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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6Ec-Nw4GORdBnS10PQFWS4BfooJpZg3J9tD3RKbXAENg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=bjorn@openias.org \
--cc=linux-wireless@vger.kernel.org \
--cc=make-wifi-fast@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