From: Ben Greear <greearb@candelatech.com>
To: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
Johannes Berg <johannes@sipsolutions.net>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>,
Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
Subject: Re: [PATCH 1/2] nl80211: add support for mcs masks
Date: Tue, 20 Dec 2011 07:03:29 -0800 [thread overview]
Message-ID: <4EF0A3C1.7050302@candelatech.com> (raw)
In-Reply-To: <20111219211423.GA24764@pandem0nium>
On 12/19/2011 01:14 PM, Simon Wunderlich wrote:
> Hello Ben,
>
> On Mon, Dec 19, 2011 at 07:28:52AM -0800, Ben Greear wrote:
>> On 12/19/2011 06:14 AM, Simon Wunderlich wrote:
>>> Allow to set mcs masks through nl80211. We also allow to set MCS
>>> rates but no legacy rates (and vice versa).
>>
>> Can you not use the ht-caps logic that went in recently? I was able
>> to successfully set station MCS rates with it. It only works for
>> station devices at this point...but AP support could probably be
>> added without too much trouble.
>
> I have not tried that out yet, but one important side effect we are
> using here is to force HT mode, also for No Ack packets which are
> usually sent with the lowest (legacy) rate. We are building fixed
> links and want to set a fixed HT rate there, and only this rate should
> be used whenever possible (and no legacy rates).
The ht-caps patch gives the ability to specify the available MCS rates
(again, for stations only at this point). I didn't try forcing speeds
higher, but I did test that it could force speeds lower. It requires
a patch to hostapd that I've posted, but it has not yet been accepted.
There is no way to disable legacy rates in the current code, as far
as I know.
>
> As far as I understand, the ht caps overrides will only override
> HT configurations, but what I want is to also let the rate matcher
> consider HT rates too and to disable legacy rates completely.
>
> As the mcs masks support has been prepared a long time ago in iw and
> mac80211, it did not seem to be the worst idea to finally fill this
> gap and implement it. :)
I haven't read your patch in detail, and at the least, the ht-caps code
would need some additional work to support your needs. So, I'm not
sure whether working on top of the ht-caps logic is useful or not.
Likely Johannes will have more useful feedback when he gets the time.
I will try to read your patch in more detail when I get a chance.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-12-20 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 14:14 [PATCH 0/2] add support for mcs masks Simon Wunderlich
2011-12-19 14:14 ` [PATCH 1/2] nl80211: " Simon Wunderlich
2011-12-19 15:28 ` Ben Greear
2011-12-19 21:14 ` Simon Wunderlich
2011-12-20 15:03 ` Ben Greear [this message]
2012-01-03 14:20 ` Johannes Berg
2011-12-19 14:14 ` [PATCH 2/2] mac80211: " Simon Wunderlich
2012-01-03 14:24 ` Johannes Berg
2012-01-04 16:51 ` Simon Wunderlich
2012-01-04 17:01 ` Johannes Berg
2011-12-19 14:14 ` [PATCH 1/2] iw: add nl80211 bitrates Simon Wunderlich
2011-12-19 14:14 ` [PATCH 2/2] iw: remove ifdefs for mcs mask Simon Wunderlich
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=4EF0A3C1.7050302@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
/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).