From: Felix Fietkau <nbd@openwrt.org>
To: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
Johannes Berg <johannes@sipsolutions.net>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>,
Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
Subject: Re: [PATCH] mac80211: Add NoAck per WMM Queue Support
Date: Wed, 16 Nov 2011 08:46:30 +0100 [thread overview]
Message-ID: <4EC36A56.70104@openwrt.org> (raw)
In-Reply-To: <1321399276-3585-1-git-send-email-siwu@hrz.tu-chemnitz.de>
On 2011-11-16 12:21 AM, Simon Wunderlich wrote:
> This patch adds support for NoAck per WMM Queue. The Unicast QoS
> Header is adapted accordingly for each outgoing frame.
> The support is turned on and off through nl80211 by extending
> the WMM TX Queue Parameters, but can be triggered separately.
>
> I have tested this feature on ath9k as well as ath5k devices. There is
> an iw patch as well to make use of this feature.
>
> It should apply well on the latest wireless-testing kernel.
>
> Signed-off-by: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
> Signed-off-by: Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
> ---
> include/linux/nl80211.h | 2 ++
> include/net/cfg80211.h | 7 +++++++
> include/net/mac80211.h | 2 ++
> net/mac80211/cfg.c | 21 +++++++++++++++++++++
> net/mac80211/tx.c | 5 +++++
> net/mac80211/util.c | 1 +
> net/mac80211/wme.c | 5 ++++-
> net/wireless/nl80211.c | 34 +++++++++++++++++++++++++++++-----
> 8 files changed, 71 insertions(+), 6 deletions(-)
>
> @@ -832,6 +833,7 @@ struct ieee80211_txq_params {
> u16 cwmin;
> u16 cwmax;
> u8 aifs;
> + bool noack;
> };
>
> /* from net/wireless.h */
> @@ -1341,6 +1343,8 @@ struct cfg80211_gtk_rekey_data {
> *
> * @set_txq_params: Set TX queue parameters
> *
> + * @set_txq_noack: Set TX queue NoAck Parameter
> + *
> * @set_channel: Set channel for a given wireless interface. Some devices
> * may support multi-channel operation (by channel hopping) so cfg80211
> * doesn't verify much. Note, however, that the passed netdev may be
> @@ -1521,6 +1525,9 @@ struct cfg80211_ops {
> int (*set_txq_params)(struct wiphy *wiphy, struct net_device *dev,
> struct ieee80211_txq_params *params);
>
> + int (*set_txq_noack)(struct wiphy *wiphy, struct net_device *dev,
> + struct ieee80211_txq_params *params);
> +
> int (*set_channel)(struct wiphy *wiphy, struct net_device *dev,
> struct ieee80211_channel *chan,
> enum nl80211_channel_type channel_type);
Why add a separate cfg80211 op when you can just make use of the extra
parameter in the existing one?
- Felix
next prev parent reply other threads:[~2011-11-16 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 23:21 [PATCH] mac80211: Add NoAck per WMM Queue Support Simon Wunderlich
2011-11-15 23:21 ` [PATCH] iw: add support for wmm NoAck per WMM Queue Simon Wunderlich
2011-11-16 7:46 ` Felix Fietkau [this message]
2011-11-16 7:50 ` [PATCH] mac80211: Add NoAck per WMM Queue Support Johannes Berg
2011-11-16 7:52 ` Johannes Berg
2011-11-16 10:51 ` Simon Wunderlich
2011-11-16 10:57 ` Johannes Berg
2011-11-16 12:29 ` Simon Wunderlich
2011-11-16 13:58 ` Helmut Schaa
2011-11-16 15:21 ` Simon Wunderlich
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=4EC36A56.70104@openwrt.org \
--to=nbd@openwrt.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
/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).