From: Aloka Dixit <alokad@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, John Crispin <john@phrozen.org>,
kernel test robot <lkp@intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v9 1/4] nl80211: add basic multiple bssid support
Date: Thu, 08 Apr 2021 10:09:58 -0700 [thread overview]
Message-ID: <7b078e1b3aea52b3449b3f8398c084ef@codeaurora.org> (raw)
In-Reply-To: <79c9b9c0577e6635f6e2e737f824f5962f25cd20.camel@sipsolutions.net>
On 2021-04-08 05:05, Johannes Berg wrote:
> On Wed, 2021-03-10 at 10:26 -0800, Aloka Dixit wrote:
>>
>> +/**
>> + * struct cfg80211_multiple_bssid - AP settings for multi bssid
>> + *
>> + * @index: the index of this AP in the multi bssid group.
>> + * @count: the total number of multi bssid peer APs.
>> + * @parent: non-transmitted BSSs transmitted parents index
>> + * @ema: Shall the beacons be sent out in EMA mode.
>> + */
>> +struct cfg80211_multiple_bssid {
>> + u8 index;
>> + u8 count;
>> + u32 parent;
>> + bool ema;
>> +};
>
> Can reorder this to make it smaller: bool before u32), or even u32
> element first.
>
Will do.
>> +/**
>> + * struct cfg80211_multiple_bssid_data - Multiple BSSID elements
>> + *
>> + * @cnt: Number of elements in array %elems.
>> + *
>> + * @elems: Array of multiple BSSID element(s) to be added into Beacon
>> frames.
>> + * @elems.data: Data for multiple BSSID elements.
>> + * @elems.len: Length of data.
>> + */
>> +struct cfg80211_multiple_bssid_data {
>> + u8 cnt;
>> + struct {
>> + u8 *data;
>> + size_t len;
>> + } elems[];
>> +};
>
> Why are the elements separate, rather than a single big buffer with all
> elements?
>
>
This is for EMA AP where each element will hold different
non-transmitted profiles. While copying elements in
ieee80211_assign_beacon(), all are copied one by one.
However during beacon generation in __ieee80211_beacon_get(),
only the element at a given index is actually added.
Hence separate elements.
>> + * @multiple_bssid.max_num_vaps: Maximum number of VAPS supported by
>> the driver
>
> Please use upstream terminology, we don't use the term "VAP" (and
> "VAPS"
> would be wrong anyway, "VAPs").
>
> I'd probably call this "max_interfaces", maybe we'll extend this to
> other things (mesh?) later?
>>
Will change.
>> +/**
>> + * enum nl80211_multiple_bssid_elems_attributes - Attributes used to
>> pass
>> + * multiple BSSID elements data.
>> + *
>> + * @__NL80211_MULTIPLE_BSSID_ELEMS_ATTR_INVALID: Invalid
>> + *
>> + * @NL80211_MULTIPLE_BSSID_ELEMS_ATTR_COUNT: Number of multiple BSSID
>> + * elements (u8).
>> + *
>> + * @NL80211_MULTIPLE_BSSID_ELEMS_ATTR_DATA: Array of multiple BSSID
>> elements.
>> + */
>> +enum nl80211_multiple_bssid_elems_attributes {
>> + __NL80211_MULTIPLE_BSSID_ELEMS_ATTR_INVALID,
>> +
>> + NL80211_MULTIPLE_BSSID_ELEMS_ATTR_COUNT,
>> + NL80211_MULTIPLE_BSSID_ELEMS_ATTR_DATA,
>>
>
> Can you clarify why this is an array? See also above.
>
>
> johannes
Array to pass separate MBSSID elements for EMA which will
hold different profiles in the same MBSSID set.
next prev parent reply other threads:[~2021-04-08 17:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 18:26 [PATCH v9 0/4] Multiple BSSID support Aloka Dixit
2021-03-10 18:26 ` [PATCH v9 1/4] nl80211: add basic multiple bssid support Aloka Dixit
2021-04-08 12:05 ` Johannes Berg
2021-04-08 17:09 ` Aloka Dixit [this message]
2021-03-10 18:26 ` [PATCH v9 2/4] mac80211: add multiple bssid support to interface handling Aloka Dixit
2021-04-08 12:06 ` Johannes Berg
2021-04-16 21:35 ` Aloka Dixit
2021-04-19 11:28 ` Johannes Berg
2021-04-19 22:35 ` Aloka Dixit
2021-04-19 22:42 ` Aloka Dixit
2021-04-20 8:25 ` Johannes Berg
2021-03-10 18:26 ` [PATCH v9 3/4] mac80211: add multiple bssid/EMA support to beacon handling Aloka Dixit
2021-04-08 12:11 ` Johannes Berg
2021-04-08 17:16 ` Aloka Dixit
2021-03-10 18:26 ` [PATCH v9 4/4] mac80211: CSA on non-transmitting interfaces Aloka Dixit
2021-04-08 11:53 ` [PATCH v9 0/4] Multiple BSSID support Johannes Berg
2021-04-09 18:05 ` Aloka Dixit
2021-04-08 12:17 ` Johannes Berg
2021-04-09 18:31 ` Aloka Dixit
2021-04-09 19:28 ` 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=7b078e1b3aea52b3449b3f8398c084ef@codeaurora.org \
--to=alokad@codeaurora.org \
--cc=dan.carpenter@oracle.com \
--cc=johannes@sipsolutions.net \
--cc=john@phrozen.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.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).