From: Joshua Zhao <swzhao@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] tx queue stuck for many minutes
Date: Thu, 11 Apr 2019 17:04:04 -0700 [thread overview]
Message-ID: <CAKmTU=qT4jLrcNqxUSO=qwDo_Th9Rf7TEQd3kOH+a-i-5kyJRw@mail.gmail.com> (raw)
In-Reply-To: <CAKmTU=opd0wLy6jWvQA37O4nHVxxUFdT79BGcdKVfpgYN4zf9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
and, BTW, what's best way to disable or skip AQM for comparison purposes?
Thanks!
Joshua
On Thu, Apr 11, 2019 at 4:38 PM Joshua Zhao <swzhao@gmail.com> wrote:
> Hi,
> I run into a weird symptom that occasionally the aqm tx queue can get
> stuck for quite long time (maybe around 30min). What happened is that
> we're sending a low bandwidth UDP traffic from the host to multiple peers
> over a WiFi radio simultaneously. We're running opensource mac80211 +
> ath10k driver. Very occasionally when there are temporary issues causing
> trouble on the host sending to one of the peers, the queue to all peers can
> get stuck and stay stuck for quite long (even though the link trouble had
> been gone or TX had been stopped). Only after quite a while, then the queue
> cleans up.
> The following dump shows an example that the backlog-packets count stays
> at 74 for around 30min after the TX had totally stopped. Here when video
> queue is stuck, other TID's traffic can go through.
> I wonder why it takes so long for the queue to clean up. Shouldn't packets
> be dropped quickly if they cannot be sent?
>
> Many thanks!
>
> cat /sys/kernel/debug/ieee80211/phy0/netdev:wlan3/stations/xx:xx:xx/aqm
>
> target 19999us interval 99999us ecn yes
>
> tid ac backlog-bytes backlog-packets new-flows drops marks overlimit
> collisions tx-bytes tx-packets
>
> 0 2 0 0 3 0 0 0 0 390 3
>
> 1 3 0 0 0 0 0 0 0 0 0
>
> 2 3 0 0 0 0 0 0 0 0 0
>
> 3 2 0 0 0 0 0 0 0 0 0
>
> 4 1 0 0 0 0 0 0 0 0 0
>
> 5 1 112344 74 1627 0 0 0 0 2373618 1632
>
> 6 0 0 0 0 0 0 0 0 0 0
>
> 7 0 0 0 1 0 0 0 0 32 1
>
> 8 2 0 0 0 0 0 0 0 0 0
>
> 9 3 0 0 0 0 0 0 0 0 0
>
> 10 3 0 0 0 0 0 0 0 0 0
>
> 11 2 0 0 0 0 0 0 0 0 0
>
> 12 1 0 0 0 0 0 0 0 0 0
>
> 13 1 0 0 0 0 0 0 0 0 0
>
> 14 0 0 0 0 0 0 0 0 0 0
>
> 15 0 0 0 0 0 0 0 0 0 0
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2292 bytes --]
next prev parent reply other threads:[~2019-04-12 0:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 23:38 Joshua Zhao
2019-04-12 0:04 ` Joshua Zhao [this message]
2019-04-12 9:18 ` Toke Høiland-Jørgensen
2019-04-12 17:26 ` Joshua Zhao
2019-04-12 19:57 ` Toke Høiland-Jørgensen
2019-04-12 23:03 ` Joshua Zhao
2019-04-13 6:45 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKmTU=qT4jLrcNqxUSO=qwDo_Th9Rf7TEQd3kOH+a-i-5kyJRw@mail.gmail.com' \
--to=swzhao@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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