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 18:07:34 +0100 [thread overview]
Message-ID: <c95e9e9f5539150459f97f811b784a6e9af163cf.camel@sipsolutions.net> (raw)
In-Reply-To: <20191108160121.tbatmqwx64aoqqai@bars>
On Fri, 2019-11-08 at 16:01 +0000, Sergey Matyukevich wrote:
> > 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
>
> Hmmm... Logic is straightforwad without this flag:
> - settings are applied to bitmasked TIDs of a single peer if address is specifed
> - settings are applied to bitmasked TIDs of all the peers if no address is specified
Sure, this is obvious, but what exactly does "all the peers" mean?
Say I do
set_tid_config(tids=0x1, peer=02:11:22:33:44:55, noack=yes)
set_tid_config(tids=0x1, peer=NULL, noack=no)
Does that reset peer 02:11:22:33:44:55, or not? This is not documented
right now, and one could argue both ways - the override for that
particular peer should stick, or should be removed. Which one is it?
> It looks like you want to infer too much from a single flag. Why keep this logic in
> cfg80211/mac80211/driver ?
I just want to disambiguate what "all the peers" means. Not sure what
you mean by keeping the logic?
johannes
next prev parent reply other threads:[~2019-11-08 17:07 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
2019-11-08 16:01 ` Sergey Matyukevich
2019-11-08 17:07 ` Johannes Berg [this message]
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=c95e9e9f5539150459f97f811b784a6e9af163cf.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).