> Add infrastructure to support per TID configurations like noack policy, > retry count, AMPDU control(disable/enable), RTSCTS control(enable/disable) > and TX rate mask configurations. > This will be useful for the driver which can supports data TID > specific configuration rather than phy level configurations. > Here NL80211_CMD_SET_TID_CONFIG added to support this operation by > accepting TID configuration. > This command can accept STA mac addreess to make the configuration > station specific rather than applying to all the connected stations > to the netdev. > And this nested command configuration can accept multiple number of > data TID specific configuration in a single command, > enum ieee80211_tid_conf_mask used to notify the driver that which > configuration got modified for the TID. > > Tamizh chelvam (6): > nl80211: New netlink command for TID specific configuration > nl80211: Add new netlink attribute for TID speicific retry count > nl80211: Add netlink attribute for AMPDU aggregation enable/disable > nl80211: Add netlink attribute to enable/disable RTS_CTS > nl80211: Add netlink attribute to configure TID specific tx rate > mac80211: Add api to support configuring TID specific configuration > > include/net/cfg80211.h | 55 +++++++++ > include/net/mac80211.h | 8 ++ > include/uapi/linux/nl80211.h | 190 +++++++++++++++++++++++++++++ > net/mac80211/cfg.c | 28 +++++ > net/mac80211/driver-ops.h | 15 +++ > net/wireless/nl80211.c | 276 +++++++++++++++++++++++++++++++++++++++--- > net/wireless/rdev-ops.h | 12 ++ > net/wireless/trace.h | 17 +++ > 8 files changed, 584 insertions(+), 17 deletions(-) Hi Tamizh, Johannes, and all, Looks very good to me: Reviewed-by: Sergey Matyukevich <sergey.matyukevich.os@xxxxxxxxxxxxx> BTW, there are two open questions remaining from the previous reviews: - NL80211_TX_RATE_LIMITED and NL80211_TX_RATE_FIXED Interpretation and validation of these two rate options is left up to drivers. - 'apply to all TIDs' usecase Currently, if peer is not specified, then configuration is applied to all the connected STAs. It is tempting to use some spare TID value to inform drivers that provided configuration should be applied to all TIDs of the specified STA or even to all TIDS and STAs. But that can not be left up to drivers since this value needs to be passed from userspace tools, e.g. from iw. IIUC, the first question could be addressed later, after we see some actual users and figure out generic use-cases. But what about the second question ? Maybe it worth to add and document a single define, e.g. using TID value 0xff, that can be used between userspace and drivers for such usecases ? Regards, Sergey
