DragonFly kernel List (threaded) for 2010-03
From: Rui Paulo <firstname.lastname@example.org>
Subject: Re: wlan_ratectl (was Re: firmware discussion)
Date: Tue, 30 Mar 2010 20:54:14 +0100
MIME-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
X-Trace: 1269979486 crater_reader.dragonflybsd.org 55374 18.104.22.168
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:14201
On 30 Mar 2010, at 20:03, Joe Talbott wrote:
> On Tue, Mar 30, 2010 at 07:30:50PM +0100, Rui Paulo wrote:
>> On 30 Mar 2010, at 18:44, Joe Talbott wrote:
>>> On Tue, Mar 30, 2010 at 10:30:06AM -0700, Matthew Dillon wrote:
>>>> I'd have to agree with Rui here. We have no choice if the code would
>>>> otherwise be unmaintained.
>>> I'm still unclear on this. Does FreeBSD currently have rate control
>>> algorithms for drivers other than ath?
>> Yes, for example ral uses AMRR only. But the wlan_ratectl on DragonFly allowed drivers to use ath's rate control algorithms.
> What are the arguments for not factoring out the rate control
There are no arguments. What happened was that no one thought it was a priority and it didn't get done.
> What are the chances of getting this into FreeBSD as
This won't get into FreeBSD as is. The fact is that we have a small amount of code to handle with the rate control framework, but the rate control framework isn't written yet.
I'll chat with Sam and if I develop a rate control framework that interacts with the code already in FreeBSD will that be good for you?