From: vthiagar@codeaurora.org
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-wireless-owner@vger.kernel.org
Subject: Re: [RFC 2/4] nl80211/mac80211: Extend NoAck policy command with peer MAC address
Date: Wed, 28 Mar 2018 10:24:43 +0530 [thread overview]
Message-ID: <bf1c7f4dc442e0e2807b520fe94d7ca2@codeaurora.org> (raw)
In-Reply-To: <1522154870.3050.2.camel@sipsolutions.net>
On 2018-03-27 18:17, Johannes Berg wrote:
> On Tue, 2018-03-27 at 14:12 +0530, Vasanthakumar Thiagarajan wrote:
>>
>> - * @set_noack_map: Set the NoAck Map for the TIDs.
>> + * @set_noack_map: Set the NoAck Map for the TIDs. When peer is not
>> %NULL NoAck
>> + * map will be applied for that particular peer. When peer is %NULL
>> NoAck
>> + * map will be applied for all the connected stations (except the
>> ones
>> + * which already have per-peer TID map configured) on the netdev.
>> + * Driver should return -ENOSPC when the it does not have room for
>> + * additional entries for per-peer NoAck map.
>
> I guess it should also set the default for new stations when the peer
> is
> not given? At least that's how mac80211 would behave now, afaict.
Sure. May be setting -1 as the default value when the per-peer NoAck
policy is not
set would work.
>
> The question is how that interacts with having enough space - are you
> sure this is a concern?
This will not be an issue at lest for ath10k. This is mainly for a
(new)driver
which implements the offload but has limitation in supporting more than
certain
number of peers. Perhaps we can remove it now and add it when such
driver is
available?
>
>> * @NL80211_CMD_SET_NOACK_MAP: sets a bitmap for the individual TIDs
>> whether
>> - * No Acknowledgement Policy should be applied.
>> + * No Acknowledgement Policy should be applied. %NL80211_ATTR_MAC is
>> used
>> + * to apply No Acknowledgement policy for a particular connected
>> station.
>> + * Station specific NoAck policy configuration is valid only for
>> STA's
>> + * current connection, i.e. the configuration will not be used when
>> the
>> + * station connects back after disconnection/roaming.
>> + * When user-space does not include %NL80211_ATTR_MAC, the No
>> + * Acknowledgement Policy setting should be treated as per-netdev
>> + * configuration.
>
> Here you describe different semantics - i.e. you didn't describe the
> "previous per-station settings are kept" part. I'm not sure that part
> makes much sense anyhow?
Not sure I got this comment right. As mentioned in the doc, the previous
settings
would be reset upon reconnection of the station and any ndev wide
configuration
will be used. As mentioned above, additionally default value will be set
to the
station to mark no per-station configuration is given so far.
Vasanth
next prev parent reply other threads:[~2018-03-28 4:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 8:42 [RFC 0/4] wireless: Per-sta NoAck and offload support Vasanthakumar Thiagarajan
2018-03-27 8:42 ` [RFC 1/4] mac80211: Add NoAck policy functionality offload infrastructure Vasanthakumar Thiagarajan
2018-03-27 12:53 ` Johannes Berg
2018-03-28 5:35 ` vthiagar
2018-03-27 8:42 ` [RFC 2/4] nl80211/mac80211: Extend NoAck policy command with peer MAC address Vasanthakumar Thiagarajan
2018-03-27 12:47 ` Johannes Berg
2018-03-28 4:54 ` vthiagar [this message]
2018-03-28 8:06 ` Johannes Berg
2018-03-28 8:50 ` vthiagar
2018-03-28 8:52 ` Johannes Berg
2018-03-27 8:42 ` [RFC 3/4] mac80211: Apply per-peer NoAck tid bitmap configuration Vasanthakumar Thiagarajan
2018-03-27 12:54 ` Johannes Berg
2018-03-28 5:43 ` vthiagar
2018-03-28 8:04 ` Johannes Berg
2018-03-29 5:31 ` vthiagar
2018-03-27 8:42 ` [RFC 4/4] mac80211: Advertise per-peer NoAck policy support Vasanthakumar Thiagarajan
2018-03-27 16:48 ` [RFC 0/4] wireless: Per-sta NoAck and offload support Steve deRosier
2018-03-28 6:09 ` vthiagar
2018-03-28 7:37 ` Arend van Spriel
2018-03-28 7:59 ` vthiagar
2018-03-28 8:03 ` Johannes Berg
2018-03-28 15:12 ` Steve deRosier
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=bf1c7f4dc442e0e2807b520fe94d7ca2@codeaurora.org \
--to=vthiagar@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless-owner@vger.kernel.org \
--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).