From: Neal Cardwell <ncardwell@google.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Eric Dumazet" <eric.dumazet@gmail.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
linux-wireless@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: debugging TCP stalls on high-speed wifi
Date: Thu, 12 Dec 2019 10:11:14 -0500 [thread overview]
Message-ID: <CADVnQym_CNktZ917q0-9dVY9dhtiJVRRotGTrPNdZUpkjd3vyw@mail.gmail.com> (raw)
In-Reply-To: <14cedbb9300f887fecc399ebcdb70c153955f876.camel@sipsolutions.net>
On Thu, Dec 12, 2019 at 9:50 AM Johannes Berg <johannes@sipsolutions.net> wrote:
> If you have any thoughts on this, I'd appreciate it.
Thanks for the detailed report!
I was curious:
o What's the sender's qdisc configuration?
o Would you be able to log periodic dumps (e.g. every 50ms or 100ms)
of the test connection using a recent "ss" binary and "ss -tinm", to
hopefully get a sense of buffer parameters, and whether the flow in
these cases is being cwnd-limited, pacing-limited,
send-buffer-limited, or receive-window-limited?
o Would you be able to share a headers-only tcpdump pcap trace?
thanks,
neal
next prev parent reply other threads:[~2019-12-12 15:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 14:50 debugging TCP stalls on high-speed wifi Johannes Berg
2019-12-12 15:11 ` Neal Cardwell [this message]
2019-12-12 15:47 ` Johannes Berg
2019-12-12 18:11 ` Eric Dumazet
2019-12-12 21:11 ` Johannes Berg
2019-12-12 21:29 ` Ben Greear
2019-12-12 21:46 ` Johannes Berg
2019-12-12 21:58 ` Ben Greear
2019-12-12 21:50 ` Eric Dumazet
2019-12-12 21:53 ` Johannes Berg
2019-12-12 23:42 ` Dave Taht
2019-12-13 0:59 ` [Make-wifi-fast] " Simon Barber
2019-12-13 1:46 ` Eric Dumazet
2019-12-13 1:57 ` Simon Barber
2019-12-13 4:42 ` Dave Taht
2019-12-13 8:08 ` Johannes Berg
2019-12-13 9:10 ` Krishna Chaitanya
2020-01-24 10:34 ` Johannes Berg
2020-01-24 23:49 ` Eric Dumazet
2019-12-13 4:15 ` Justin Capella
2019-12-13 7:43 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2019-12-16 18:14 Simon Barber
2019-12-16 19:20 ` Eric Dumazet
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=CADVnQym_CNktZ917q0-9dVY9dhtiJVRRotGTrPNdZUpkjd3vyw@mail.gmail.com \
--to=ncardwell@google.com \
--cc=eric.dumazet@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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).