From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Joshua Zhao <swzhao@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] tx queue stuck for many minutes
Date: Sat, 13 Apr 2019 08:45:06 +0200 [thread overview]
Message-ID: <87d0lqwgi5.fsf@toke.dk> (raw)
In-Reply-To: <CAKmTU=oScLc_ji6pkP5r+jjbsSeWfbBcXjGjE7+Ab8-ej+gY0g@mail.gmail.com>
Joshua Zhao <swzhao@gmail.com> writes:
> That makes sense. I guess missing TX completion could be potential suspect
> and I'll check on that.
>
> On the other hand, why I ask about back-pressure is because when the
> problem happens the UDP TX socket shows as stuck and doesn't take any new
> packets.
>
> ~# netstat -tulnp
>
> Active Internet connections (only servers)
>
> Proto Recv-Q Send-Q Local Address Foreign Address State
> PID/Program name
>
> udp 0 22400 0.0.0.0:48439 0.0.0.0:*
> 2407/audiod-xxxxx
>
> Basically the "Send-Q" number stays as a very high number for long time (I
> didn't save what the exact number is when the problem happens) in the above
> example, so that the sendto() function simply fails.
> This is why I wondered about back-pressure being applied. Otherwise
> shouldn't UDP socket keeps sending and packets would be dropped by the
> queue scheduler?
I would expect so; mac80211 only ever returns NETDEV_TX_OK from its
netif_start_xmit() function. Guess the socket layer can stall out for
some reason, or something?
-Toke
prev parent reply other threads:[~2019-04-13 7:11 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
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 [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
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=87d0lqwgi5.fsf@toke.dk \
--to=toke@redhat.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=swzhao@gmail.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