From: Felix Fietkau <nbd@openwrt.org>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH 3.14] ath9k: fix ps-poll responses under a-mpdu sessions
Date: Tue, 11 Mar 2014 10:36:33 +0100 [thread overview]
Message-ID: <531ED921.5040601@openwrt.org> (raw)
In-Reply-To: <CAGXE3d_wmuDi2kUjvhLGxSFMAxwcYgjLXJ78fPgyHmDN7m0cSw@mail.gmail.com>
On 2014-03-11 10:28, Helmut Schaa wrote:
> On Sat, Feb 22, 2014 at 1:48 PM, Felix Fietkau <nbd@openwrt.org> wrote:
>> When passing tx frames to the U-APSD queue for powersave poll responses,
>> the ath_atx_tid pointer needs to be passed to ath_tx_setup_buffer for
>> proper sequence number accounting.
>>
>> This fixes high latency and connection stability issues with ath9k
>> running as AP and a few kinds of mobile phones as client, when PS-Poll
>> is heavily used
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>> ---
>
> Hi Felix,
>
> this commit introduced a regression for me when using Intel Win7
> clients on a ath9k AP.
>
> I was not able to track the exact issue down yet :( but it seems to be
> related to the Intel
> client constantly tearing down the BA session and entering/leaving PS mode.
>
> Any idea?
Please make some packet captures and describe more clearly what the
regression is. Do you see connections stalling, big latencies, etc?
- Felix
next prev parent reply other threads:[~2014-03-11 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 12:48 [PATCH 3.14] ath9k: fix ps-poll responses under a-mpdu sessions Felix Fietkau
2014-03-11 9:28 ` Helmut Schaa
2014-03-11 9:36 ` Felix Fietkau [this message]
2014-03-11 14:22 ` Helmut Schaa
2014-03-11 15:16 ` Felix Fietkau
2014-03-11 15:37 ` Helmut Schaa
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=531ED921.5040601@openwrt.org \
--to=nbd@openwrt.org \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).