From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
Cc: 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:52:15 +0100 [thread overview]
Message-ID: <1321429935.4773.10.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1321399276-3585-1-git-send-email-siwu@hrz.tu-chemnitz.de>
On Wed, 2011-11-16 at 00:21 +0100, 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.
Can you explain what for? :-)
I'm not sure this API is really the best way to handle it either, like I
just said it might be nicer per connection or so to get reset properly.
> 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.
Since you're adding 'real API' (unlike the debugfs file which you should
probably remove now!) you also should think about drivers like mwifiex
that don't support this and don't use mac80211.
Also, given real API, this impacts the duration calculation etc.
johannes
next prev parent reply other threads:[~2011-11-16 7:52 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
2011-11-16 7:52 ` Johannes Berg [this message]
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=1321429935.4773.10.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=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.