From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Debugging very slow ath9k AP performance
Date: Thu, 05 Apr 2012 18:13:59 -0700 [thread overview]
Message-ID: <4F7E4357.6080608@candelatech.com> (raw)
In-Reply-To: <4F7E288F.9060306@candelatech.com>
On 04/05/2012 04:19 PM, Ben Greear wrote:
> On 04/05/2012 04:12 PM, Ben Greear wrote:
>> I am seeing very slow performance when I have around 100
>> stations connected to an AP (ath9k on both ends).
>>
>> It seems like the station side is doing fine, but on the
>> AP side, it appears there are always lots of pending frames
>> and it is only transmitting about 100 pkts per second if my stats
>> are correct.
>>
>> Kernel is 3.3.1+ with the troublesome ath9k patch reverted.
>>
>> I would be greatful for any pointers as to what might be
>> causing this slowdown.
>
> Hrm, just noticed dmesg is full of these messages:
>
> ieee80211 wiphy0: dropped TX filtered frame, queue_len=0 PS=0 @7658178
> ieee80211 wiphy0: dropped TX filtered frame, queue_len=0 PS=0 @7658178
> net_ratelimit: 33 callbacks suppressed
> ieee80211 wiphy0: dropped TX filtered frame, queue_len=0 PS=0 @7671545
>
> Will have to go figure out what that means...
Ok, I think the reason is just that the channel was too crowded.
Signal and noise and 'quality' were good..but way too many retries
and failed retries. Seems the AP has more issues than the client
for whatever reason, but moving to a different channel made it all
better again.
Seems like I do this to myself every few months...hopefully I'll
figure it out before spamming the list next time.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2012-04-06 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 23:12 [ath9k-devel] Debugging very slow ath9k AP performance Ben Greear
2012-04-05 23:19 ` Ben Greear
2012-04-06 1:13 ` Ben Greear [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=4F7E4357.6080608@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@lists.ath9k.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 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.