[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43e72e890806261435t3d06e955x590a6fafb223bbca@mail.gmail.com>
Date: Thu, 26 Jun 2008 14:35:42 -0700
From: "Luis R. Rodriguez" <mcgrof@...il.com>
To: "John W. Linville" <linville@...driver.com>
Cc: "Adrian Bunk" <bunk@...nel.org>,
"Johannes Berg" <johannes@...solutions.net>,
"Adrian Bunk" <bunk@...sta.de>, linux-wireless@...r.kernel.org,
netdev@...r.kernel.org,
"Rindjunsky, Ron" <ron.rindjunsky@...el.com>,
"Winkler, Tomas" <tomas.winkler@...el.com>
Subject: Re: RFC: always enable MAC80211_RC_PID?
On Tue, Jun 24, 2008 at 2:12 PM, John W. Linville
<linville@...driver.com> wrote:
> On Tue, Jun 24, 2008 at 03:43:14PM +0300, Adrian Bunk wrote:
>
>> Can we get one of either:
>> - all selected mac80211 algorithms are built into the mac80211 module or
>
> This seems fine to me.
OK so just to be clear -- moving forward we strive to not allow driver
specific rate control algorithms and push out current ones into
mac80211? This would mean we don't have to *cleanup* support for
driver specific RCs but instead just have them stashed in as part of
the build. The difficulty here lies in ensuring they do work for well
for other drivers but I do agree it strives to cleanup RC code. I
think vendors also tend to use a few driver specific tweaks to boost
their own throughput in their own RCs though. Can't say for sure right
now of specific details but I'll try to get back to you with them.
Perhaps Tomas can say more about that for iwl's RCs.
Luis
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists