From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs.
Date: Tue, 21 Jun 2016 07:19:23 -0700 [thread overview]
Message-ID: <57694CEB.1050200@candelatech.com> (raw)
In-Reply-To: <1466502039.3170.16.camel@sipsolutions.net>
On 06/21/2016 02:40 AM, Johannes Berg wrote:
> On Fri, 2016-06-10 at 11:43 -0700, Ben Greear wrote:
>> On 03/15/2016 01:20 PM, Johannes Berg wrote:
>>> On Tue, 2016-03-15 at 09:10 -0700, Ben Greear wrote:
>>>>
>>>> The logic I wrote is basically exactly this. It uses the
>>>> configured
>>>> rates to specify which of the hardware's rates are allowed and
>>>> disabled.
>>>>
>>>
>>> I understand that. I just take issue with the fact that we have to
>>> sprinkle "magic pixie dust" (in form of the override function
>>> calls)
>>> everywhere throughout the code.
>>>
>>> johannes
>>>
>>
>> So, I never could think up a way to make this more acceptable and
>> meet my own goals.
>>
>> Any chance I could get just the netlink enum in place, even if it is
>> called something like 'api_placeholder_x'?
>>
>
> No, I don't think I want to do that.
>
> But if you're not too worried about space consumption, you could pick a
> higher number:
>
> /* add attributes here, update the policy in nl80211.c */
>
> NL80211_ATTR_TX_ADVERT_RATEMASK = 300,
>
> __NL80211_ATTR_AFTER_LAST,
>
> We currently use about 230 attributes, so that'll give you lots of
> breathing room.
From a pure hack point of view, maybe re-purposing some already existing
attribute that has nothing to do with scanning is the way to go.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2016-06-21 14:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 17:24 [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs greearb
2015-10-20 17:24 ` [PATCH-v2 2/2] mac80211: ensure association req uses configured ratemask greearb
2016-01-26 11:18 ` Johannes Berg
2015-11-05 18:47 ` [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs Ben Greear
2015-11-05 19:04 ` Johannes Berg
2016-01-26 11:16 ` Johannes Berg
2016-01-26 15:19 ` Ben Greear
2016-02-04 9:02 ` Johannes Berg
2016-02-04 17:52 ` Ben Greear
2016-02-18 20:32 ` Johannes Berg
2016-02-18 20:40 ` Ben Greear
2016-02-18 20:45 ` Johannes Berg
2016-02-18 20:59 ` Ben Greear
2016-02-18 21:14 ` Johannes Berg
2016-02-18 21:54 ` Ben Greear
2016-02-23 11:06 ` Johannes Berg
2016-03-10 17:56 ` Ben Greear
2016-03-15 14:15 ` Johannes Berg
2016-03-15 16:10 ` Ben Greear
2016-03-15 20:20 ` Johannes Berg
2016-06-10 18:43 ` Ben Greear
2016-06-21 9:40 ` Johannes Berg
2016-06-21 14:19 ` Ben Greear [this message]
2016-03-15 14:17 ` Johannes Berg
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=57694CEB.1050200@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).