From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 7CB663B25E for ; Mon, 24 Oct 2016 11:09:16 -0400 (EDT) Received: by mail-qt0-x22b.google.com with SMTP id f6so133355174qtd.2 for ; Mon, 24 Oct 2016 08:09:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=wP7mRrYMRUHZWPoE0PqoBftyk39f3YC3YXQzVwAAdCs=; b=vqGszlaVv/ZvxYtzYkyDumFtX+T9GQPfNXNwUyxFe4no89R9IfFVeE0xA8dh8lSdqn JRL6CuNQPwy8GX6/7IvEnPn4R/VaOLTyInmnXWkC7mJMTJqNxycJSjeqqitQg+/ZsiCq ibD5vkbZ7RNGF6GFqbrFXgox5+OqY1Ea2NYTHycJvZla6KML3Dizz55b/f0YSfdp4imJ TwrGURKHTvzLF5Ab77EAK70DQdFFWJ5asIgccCLZT7B+1xyYHlRblm+/ChxoiY2XHclI kmP1J9gGJ2wUFN1sdLL/wTr4NjzjaW5OxYcV0rqCit7B2YZgfzbNUzFI5x5+Dovbe3YP 8//Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=wP7mRrYMRUHZWPoE0PqoBftyk39f3YC3YXQzVwAAdCs=; b=mVkp2WCB5EyxoyUI6jR7U6RjDgJj51dX2f3B+Hew+ZexT60PIWtjAurManhbGabEzM nN8w2I4a4pNZG3H99DXzvJw64rcT+RDF82tjT07qYNbdIt+Sxokv1S82Su0DSIxYg7jD G+cFfKkj84pHbQ/kJcDcFo4nqLD7mr8vR9Rk0HQ5kAM/VDauwjtUdyzNIZNhn38295vv RXXx4SE5iHCjABcF55vdG2K8abFTgi17Nm8vN62oFXqoE+SJRjiPa7ceEKUCya1/sAH6 81O6f4smmL4nybp9q5RHF9f33/EXsuy+ZX2T5itb/TgU/6ODt6Y+ODFwyK8KwHETTOTC 4mkA== X-Gm-Message-State: ABUngve1FzUmImFBIHGuZxVq7Z9hBWBiX4/AXVfd+F8oiLz+VvveVVzZNPAm/h1LnWC+vZC/N+f6bHJVVtGEag== X-Received: by 10.237.34.83 with SMTP id o19mr16170171qtc.15.1477321755957; Mon, 24 Oct 2016 08:09:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.146.164 with HTTP; Mon, 24 Oct 2016 08:09:15 -0700 (PDT) In-Reply-To: References: From: Dave Taht Date: Mon, 24 Oct 2016 08:09:15 -0700 Message-ID: To: =?UTF-8?Q?Bj=C3=B6rn_Smedman?= , make-wifi-fast@lists.bufferbloat.net Cc: linux-wireless , "ath9k-devel@lists.ath9k.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] Bayesian rate control X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 15:09:16 -0000 On Sun, Oct 23, 2016 at 6:57 AM, Bj=C3=B6rn Smedman wro= te: > 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 h= ere: 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=C3=B6rn Smedman --=20 Dave T=C3=A4ht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org