Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:46996 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964986AbcKOJed (ORCPT ); Tue, 15 Nov 2016 04:34:33 -0500 Message-ID: <1479202467.12007.26.camel@sipsolutions.net> (sfid-20161115_103437_220905_F616EC72) 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: Tue, 15 Nov 2016 10:34:27 +0100 In-Reply-To: (sfid-20161105_060921_458405_BB1739FB) References: <1477286912.4085.1.camel@sipsolutions.net> <1477379678.4390.2.camel@sipsolutions.net> <1477461362.4059.17.camel@sipsolutions.net> (sfid-20161105_060921_458405_BB1739FB) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: > But there is a per-descriptor TX rate table entry in the driver. > FreeBSD uses it to implement its rate control for the intel drivers. > > What am I missing? :) Not sure. But there isn't a per-descriptor table in the driver. There's a per-station table, that *can* be used in similar ways, but at least in Linux none of the APIs are hooked up to the general implementation, it's all driver/device-specific code, so it'd be very painful to try to experiment with. johannes