From: Valentin Manea <linux-wireless@mrs.ro>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
David Ross <dave@antacs.com>,
linux-wireless@vger.kernel.org
Subject: Re: mac80211 and broadcast frames
Date: Wed, 08 Jul 2009 10:30:29 +0300 [thread overview]
Message-ID: <4A544B15.8030106@mrs.ro> (raw)
In-Reply-To: <43e72e890907070915y5fd131b7l6aa845a0785f8c76@mail.gmail.com>
On 07/07/2009 07:15 PM, Luis R. Rodriguez wrote:
> On Tue, Jul 7, 2009 at 7:48 AM, John W. Linville<linville@tuxdriver.com> wrote:
>> On Tue, Jul 07, 2009 at 09:10:52PM +1000, David Ross wrote:
>>> Actually it is required to be a mutual BASIC rate (not extended rates) -
>>> not necessarily the "lowest possible" - David.
>> True, but FWIW I think all of our rate scaling algorithms choose the
>> lowest rate.
>
> And then iwlwifi and ath9k have their own rate control algo, and at
> least ath9k uses the lowest valid rate IIRC.
>
> Luis
I've found the code in ath9k and you are right, it always chooses the
lowest rate.
So, basically to transmit multicast frames at a better bitrate I have
to hack the rate control algorithm, right?
Thanks,
Valentin
next prev parent reply other threads:[~2009-07-08 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 10:53 mac80211 and broadcast frames Valentin Manea
2009-06-30 15:48 ` Valentin Manea
2009-06-30 16:20 ` Luis R. Rodriguez
2009-07-01 6:42 ` Valentin Manea
2009-07-01 8:04 ` who can share 802.11s draft Angela
2009-07-01 17:33 ` mac80211 and broadcast frames Luis R. Rodriguez
2009-07-07 8:02 ` Valentin Manea
2009-07-07 11:10 ` David Ross
2009-07-07 14:48 ` John W. Linville
2009-07-07 16:15 ` Luis R. Rodriguez
2009-07-08 7:30 ` Valentin Manea [this message]
2009-07-08 10:06 ` David Ross
2009-07-08 12:57 ` John W. Linville
2009-07-08 17:10 ` Luis R. Rodriguez
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=4A544B15.8030106@mrs.ro \
--to=linux-wireless@mrs.ro \
--cc=dave@antacs.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).