From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k-issue with stop RX/TX DMA - correlation with WMM traffic classes?
Date: Fri, 12 Apr 2013 17:41:00 +0200 [thread overview]
Message-ID: <51682B0C.2070302@openwrt.org> (raw)
In-Reply-To: <1UQZKN-00070e-F4$20130412084409Z$sl@hallo-diet.de>
On 2013-04-12 10:27 AM, Rougu wrote:
> Hi everyone,
>
> while I might be totally wrong with my observation, I still would like
> to share it, because this issue is lingering for years now and many
> users are waiting to a solid grip on it to fix it.
>
> I'm running several freifunk-nodes in Cologne, Germany, where the
> firmware contains a ath9k-watchdog that restarts the node, once the
> failure occurs. One of my nodes is affected in varying intervals of 200
> .. 10000 seconds uptime, depending on WLAN activity.
>
> (openwrt, attitude adjustment, kernel 3.3.8)
Please also run a test with OpenWrt trunk and compare stability.
> Looking at "/sys/kernel/debug/ieee80211/phy0/ath9k/xmit", it seems that
> MPDUs in the highest priority queue "VO" have a lower rate of
> "completion" (90,5%) than those in "BE" (>99,9%).
>
> From my laymen's perspective I would expect "VO" to have an even better
> completion rate than "BE".
What you're missing in that perspective is the fact that not all traffic
is created equal :)
The VO queue carries management traffic. Probe responses frequently end
up in XRetry because the number of retries is intentionally limited to 1
(some clients are often either too far away to ACK the probe response,
or do not stick around long enough to receive it).
> Any chance to see a correlation between WMM priority queue handling and
> DMA access problems?
No, the data is too limited for that.
- Felix
next prev parent reply other threads:[~2013-04-12 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 8:27 [ath9k-devel] ath9k-issue with stop RX/TX DMA - correlation with WMM traffic classes? Rougu
2013-04-12 15:41 ` Felix Fietkau [this message]
2013-04-12 16:57 ` Jan Lühr
2013-04-12 20:49 ` Felix Fietkau
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=51682B0C.2070302@openwrt.org \
--to=nbd@openwrt.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox