From: Johannes Berg <johannes@sipsolutions.net>
To: Justin Capella <justincapella@gmail.com>
Cc: "Eric Dumazet" <eric.dumazet@gmail.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: debugging TCP stalls on high-speed wifi
Date: Fri, 13 Dec 2019 08:43:26 +0100 [thread overview]
Message-ID: <90485ecbfa2a13c4438b840c8a9d37677e833ea5.camel@sipsolutions.net> (raw)
In-Reply-To: <CAMrEMU-WdaAe2wOxsnMn=npPyAjf1KkuxA8cHE==yez_rUELUQ@mail.gmail.com> (sfid-20191213_051528_721069_3C6497DE)
On Thu, 2019-12-12 at 20:15 -0800, Justin Capella wrote:
> Could TCP window size (waiting for ACKnowledgements) be a contributing factor?
Quite possibly, although even with a large number of flows?
I thought we had a TCP_CHRONO_ for it but we don't, maybe I'll try to
add one for debug.
johannes
next prev parent reply other threads:[~2019-12-13 7:43 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
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 [this message]
-- 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=90485ecbfa2a13c4438b840c8a9d37677e833ea5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eric.dumazet@gmail.com \
--cc=justincapella@gmail.com \
--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 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.