From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
linux-wireless@vger.kernel.org, linville@tuxdriver.com,
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:50:04 +0100 [thread overview]
Message-ID: <1321429804.4773.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4EC36A56.70104@openwrt.org>
On Wed, 2011-11-16 at 08:46 +0100, Felix Fietkau wrote:
> 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.
> > + 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?
Can't actually -- that one's only allowed in AP mode :)
FWIW I think this API would also better be per connection or so.
johannes
next prev parent reply other threads:[~2011-11-16 7:50 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 ` [PATCH] mac80211: Add NoAck per WMM Queue Support Felix Fietkau
2011-11-16 7:50 ` Johannes Berg [this message]
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=1321429804.4773.4.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=nbd@openwrt.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.