Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:47894 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750949AbcJZF4J (ORCPT ); Wed, 26 Oct 2016 01:56:09 -0400 Message-ID: <1477461362.4059.17.camel@sipsolutions.net> (sfid-20161026_075612_260056_D0567BD8) Subject: Re: Bayesian rate control From: Johannes Berg To: Adrian Chadd Cc: =?ISO-8859-1?Q?Bj=F6rn?= Smedman , "linux-wireless@vger.kernel.org" , ath9k-devel Date: Wed, 26 Oct 2016 07:56:02 +0200 In-Reply-To: (sfid-20161026_052554_382209_FBBBAD2D) References: <1477286912.4085.1.camel@sipsolutions.net> <1477379678.4390.2.camel@sipsolutions.net> (sfid-20161026_052554_382209_FBBBAD2D) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: > The intel 7260 and later parts also allow user controllable rate > control and provide transmit completion feedback, but I don't know > whether it's enough for your needs. Perhaps. However, existing rate control is *very* tightly coupled to the driver, and it'd be fairly pointless to disentangle just for the sake of playing with a rate control algorithm. Also, the device doesn't support per-frame control nor any kind of sampling-with-table-fallback, only the rate table that you give to the device and update. Btw, mac80211_hwsim with wmediumd doing some medium simulation might also be something to look at for just extending to VHT. And come to think of it, there's this new driver Felix et al have been working on, mt7601u, which also should support proper rate control APIs. johannes