From: Johannes Berg <johannes@sipsolutions.net>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Cc: Tamizh chelvam <tamizhr@codeaurora.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCHv8 0/6] cfg80211/mac80211: Add support for TID specific configuration
Date: Fri, 08 Nov 2019 13:20:01 +0100 [thread overview]
Message-ID: <1c553c457024b295c7d0a6b118c3848eec28bcbd.camel@sipsolutions.net> (raw)
In-Reply-To: <20191108120504.ptl25hacxcftb7tw@bars>
On Fri, 2019-11-08 at 12:05 +0000, Sergey Matyukevich wrote:
> > @NL80211_TID_CONFIG_ATTR_OVERRIDE: flag attribute, valid only if no STA
> > is selected, if set indicates that the new configuration
> > overrides all previous STA configurations, otherwise previous
> > STA-specific configurations should be left untouched
> >
> > You also raise a good point wrt. "all TIDs" - but then we should
> > probably just remove NL80211_TID_CONFIG_ATTR_TID and add a new
> > NL80211_TID_CONFIG_ATTR_TIDS as a bitmap? OTOH, it's not hard to just
> > explicitly spell out all TIDs either, I guess, just makes the message a
> > bit bigger.
>
> The idea with bitmask for TIDs looks good. It eliminates the need for both
> 'all TIDs' define and additional attribute NL80211_TID_CONFIG_ATTR_OVERRIDE.
I think we still need NL80211_TID_CONFIG_ATTR_OVERRIDE in some way
(maybe only as a flag attribute), since you could have
* change all stations (some subset of TIDs) *including* already
configured stations
* or *excluding* already configured stations
> In fact, almost no changes are needed for the patch, mostly comments need
> to be updated. Manual typing in iw will be less convenient, but I guess
> this interface is not supposed to be used by humans after all...
If that's a concern we can parse a list in iw, e.g. "0,1,2,3" instaed of
"0xf", right?
johannes
next prev parent reply other threads:[~2019-11-08 12:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 12:41 [PATCHv8 0/6] cfg80211/mac80211: Add support for TID specific configuration Tamizh chelvam
2019-11-05 12:41 ` [PATCHv8 1/6] nl80211: New netlink command " Tamizh chelvam
2019-11-08 9:55 ` Johannes Berg
2019-11-13 16:00 ` Tamizh chelvam
2019-11-22 12:47 ` Johannes Berg
2019-11-05 12:41 ` [PATCHv8 2/6] nl80211: Add new netlink attribute for TID speicific retry count Tamizh chelvam
2019-11-08 10:00 ` Johannes Berg
2019-11-14 7:20 ` Tamizh chelvam
2019-11-22 12:49 ` Johannes Berg
2019-11-05 12:41 ` [PATCHv8 3/6] nl80211: Add netlink attribute for AMPDU aggregation enable/disable Tamizh chelvam
2019-11-05 12:41 ` [PATCHv8 4/6] nl80211: Add netlink attribute to enable/disable RTS_CTS Tamizh chelvam
2019-11-05 12:41 ` [PATCHv8 5/6] nl80211: Add netlink attribute to configure TID specific tx rate Tamizh chelvam
2019-11-05 12:41 ` [PATCHv8 6/6] mac80211: Add api to support configuring TID specific configuration Tamizh chelvam
2019-11-08 9:32 ` [PATCHv8 0/6] cfg80211/mac80211: Add support for " Sergey Matyukevich
2019-11-08 9:39 ` Johannes Berg
2019-11-08 12:05 ` Sergey Matyukevich
2019-11-08 12:20 ` Johannes Berg [this message]
2019-11-08 16:01 ` Sergey Matyukevich
2019-11-08 17:07 ` Johannes Berg
2019-11-08 20:39 ` Sergey Matyukevich
2019-11-14 7:32 ` Tamizh chelvam
2019-11-22 12:49 ` 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=1c553c457024b295c7d0a6b118c3848eec28bcbd.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sergey.matyukevich.os@quantenna.com \
--cc=tamizhr@codeaurora.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).