From: Kalle Valo <kalle.valo@iki.fi>
To: tim.gardner@canonical.com
Cc: Johannes Berg <johannes@sipsolutions.net>,
reinette chatre <reinette.chatre@intel.com>,
"linville\@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] cfg80211: initialize rate control after station inserted
Date: Sat, 29 Aug 2009 08:22:46 +0300 [thread overview]
Message-ID: <874orrjis9.fsf@litku.valot.fi> (raw)
In-Reply-To: <4A984EBA.9040608@canonical.com> (Tim Gardner's message of "Fri\, 28 Aug 2009 15\:40\:10 -0600")
Tim Gardner <tim.gardner@canonical.com> writes:
>> Interesting. I've been thinking about making it go the other way --
>> remove rate scaling hooks completely. wl1271 apparently has rate scaling
>> completely in the firmware, so the RS algorithm on the host is just
>> overhead. I've been thinking putting 4965+ RS into the _driver_ makes
>> more sense since it really does a lot in the firmware and not on the
>> host.
>>
>> Do you think we should try to go that route? I'd think it would probably
>> be a hardware flag ("no RS algo please") and then we'd skip all the
>> hooks and put things into the driver. The advantage is that we don't
>> care about the mac80211 API any more, things get cleaner and we can just
>> do all RS init from sta_notify().
>>
>
> Wouldn't that make it difficult to experiment with external rate
> scaling algorithms? Not that minstrel or the other in-driver rate
> scaling algorithms always get it right, but they are certainly more
> transparent (and changeable) then firmware.
In wl1271 you are forced to use the rate scaling algorithm from the
firmware. IIRC tx descriptor doesn't even have a field for the bitrate.
--
Kalle Valo
next prev parent reply other threads:[~2009-08-29 5:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 23:34 [PATCH 1/2] cfg80211: initialize rate control after station inserted Reinette Chatre
2009-08-27 23:34 ` [PATCH 2/2] mac80211: " Reinette Chatre
2009-08-28 7:45 ` [PATCH 1/2] cfg80211: " Johannes Berg
2009-08-28 15:45 ` reinette chatre
2009-08-28 21:01 ` Johannes Berg
2009-08-28 21:26 ` Luis R. Rodriguez
2009-08-28 21:40 ` Tim Gardner
2009-08-29 5:22 ` Kalle Valo [this message]
2009-08-29 9:01 ` Johannes Berg
2009-08-28 22:18 ` reinette chatre
2009-08-29 9:34 ` Johannes Berg
2009-08-31 17:07 ` reinette chatre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874orrjis9.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.com \
--cc=tim.gardner@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.