From: Ben Greear <greearb@candelatech.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: TCP connection stops after high load.
Date: Wed, 11 Apr 2007 14:31:00 -0700 [thread overview]
Message-ID: <461D5394.9040409@candelatech.com> (raw)
In-Reply-To: <20070411.141143.82097512.davem@davemloft.net>
David Miller wrote:
> From: Ben Greear <greearb@candelatech.com>
> Date: Wed, 11 Apr 2007 14:06:31 -0700
>
>> Does the CWND == 1 count as solid? Any idea how/why this would go
>> to 1 in conjunction with the dup acks?
>>
>> For the dup acks, I see nothing *but* dup acks on the wire...going in
>> both directions interestingly, at greater than 100,000 packets per second.
>>
>> I don't mind adding printks...and I've started reading through the code,
>> but there is a lot of it, and indiscriminate printks will likely just
>> hide the problem because it will slow down performance so much.
>
> If you know that it doesn't take Einstein to figure out that maybe you
> should add logging when CWND is one and we're sending out an ACK?
>
> This is why I think you're very lazy Ben and I get very agitated with
> all of your reports, you put zero effort into thinking about how to
> debug the problem even though you know full well how to do it.
I've spent solid weeks tracking down obscure races. I'm hoping that
someone who knows the tcp stack will have some idea of places to look
based on the reported symptoms so that I don't have to spend another
solid week chasing this one. If not, so be it..I'm still working on
this between sending emails. For what it's worth, the problem (or something similar)
is reproducible on a stock FC5 .18-ish kernel as well, running between
two machines, 2 ports each.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2007-04-11 21:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 18:50 TCP connection stops after high load Ben Greear
2007-04-11 20:26 ` Ben Greear
2007-04-11 20:48 ` David Miller
2007-04-11 21:06 ` Ben Greear
2007-04-11 21:11 ` David Miller
2007-04-11 21:31 ` Ben Greear [this message]
2007-04-11 21:39 ` David Miller
2007-04-12 2:44 ` SANGTAE HA
2007-04-12 1:06 ` Benjamin LaHaise
2007-04-12 14:48 ` Andi Kleen
2007-04-12 17:59 ` Ben Greear
2007-04-12 18:19 ` Eric Dumazet
2007-04-12 19:12 ` Ben Greear
2007-04-12 20:41 ` Eric Dumazet
2007-04-12 21:36 ` Ben Greear
2007-04-13 7:09 ` Evgeniy Polyakov
2007-04-13 16:42 ` Ben Greear
2007-04-13 16:10 ` Daniel Schaffrath
2007-04-13 16:41 ` Eric Dumazet
2007-04-14 4:21 ` Herbert Xu
2007-04-14 4:25 ` David Miller
2007-04-14 5:31 ` Eric Dumazet
2007-04-14 5:37 ` David Miller
2007-04-11 20:41 ` David Miller
2007-04-12 6:12 ` Ilpo Järvinen
-- strict thread matches above, loose matches on Subject: below --
2007-04-12 21:11 Robert Iakobashvili
2007-04-12 21:15 ` David Miller
2007-04-15 12:14 ` Robert Iakobashvili
2007-04-15 15:31 ` John Heffner
2007-04-15 15:49 ` Robert Iakobashvili
2007-04-16 18:07 ` John Heffner
2007-04-16 18:51 ` Robert Iakobashvili
2007-04-16 19:11 ` John Heffner
2007-04-16 19:17 ` David Miller
2007-04-16 19:15 ` David Miller
2007-04-17 7:58 ` Robert Iakobashvili
2007-04-17 19:39 ` David Miller
2007-04-17 19:47 ` John Heffner
2007-04-17 19:51 ` David Miller
2007-04-17 19:58 ` Robert Iakobashvili
2007-04-15 13:52 ` Robert Iakobashvili
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=461D5394.9040409@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).