From: Felix Fietkau <nbd@openwrt.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
linville@tuxdriver.com, mcgrof@qca.qualcomm.com,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCH] ath9k: Test for TID only in BlockAcks while checking tx status
Date: Mon, 29 Oct 2012 15:18:48 +0100 [thread overview]
Message-ID: <508E9048.1060007@openwrt.org> (raw)
In-Reply-To: <508E77DA.8050708@openwrt.org>
On 2012-10-29 1:34 PM, Felix Fietkau wrote:
> On 2012-10-29 1:25 PM, Sven Eckelmann wrote:
>> The ath9k xmit functions for AMPDUs can send frames as non-aggregate in case
>> only one frame is currently available. The client will then answer using a
>> normal Ack instead of a BlockAck. This acknowledgement has no TID stored and
>> therefore the hardware is not able to provide us the corresponding TID.
>>
>> The TID set by the hardware in the tx status descriptor has to be seen as
>> undefined and not as a valid TID value for normal acknowledgements. Doing
>> otherwise results in a massive amount of retransmissions and stalls of
>> connections.
>>
>> Users may experience low bandwidth and complete connection stalls in
>> environments with transfers using multiple TIDs.
>>
>> This regression was introduced in b11b160defc48e4daa283f785192ea3a23a51f8e
>> ("ath9k: validate the TID in the tx status information").
>>
>> Signed-off-by: Sven Eckelmann <sven@narfation.org>
>> Signed-off-by: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
> Nice catch, thanks!
> Acked-by: Felix Fietkau <nbd@openwrt.org>
One more thing: I think this deserves a
Cc: stable@vger.kernel.org
- Felix
prev parent reply other threads:[~2012-10-29 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 12:25 [PATCH] ath9k: Test for TID only in BlockAcks while checking tx status Sven Eckelmann
2012-10-29 12:34 ` Felix Fietkau
2012-10-29 14:18 ` Felix Fietkau [this message]
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=508E9048.1060007@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@qca.qualcomm.com \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=sven@narfation.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).