From: John Heffner <jheffner@psc.edu>
To: David Miller <davem@davemloft.net>
Cc: coroberti@gmail.com, netdev@vger.kernel.org,
greearb@candelatech.com, moser.michael@gmail.com
Subject: Re: TCP connection stops after high load.
Date: Tue, 17 Apr 2007 15:47:58 -0400 [thread overview]
Message-ID: <4625246E.2090700@psc.edu> (raw)
In-Reply-To: <20070417.123941.119226635.davem@davemloft.net>
David Miller wrote:
> From: "Robert Iakobashvili" <coroberti@gmail.com>
> Date: Tue, 17 Apr 2007 10:58:04 +0300
>
>> David,
>>
>> On 4/16/07, David Miller <davem@davemloft.net> wrote:
>>>>> Commit: 53cdcc04c1e85d4e423b2822b66149b6f2e52c2c
>>>>> Author: John Heffner <jheffner@psc.edu> Fri, 16 Mar 2007 15:04:03 -0700
>>>>>
>>>>> [TCP]: Fix tcp_mem[] initialization.
>>>>> Change tcp_mem initialization function. The fraction of total memory
>>>>> is now a continuous function of memory size, and independent of page
>>>>> size.
>>>>
>>>> Kernels 2.6.19 and 2.6.20 series are effectively broken right now.
>>>> Don't you wish to patch them?
>>> Can you verify that this patch actually fixes your problem?
>> Yes, it fixes.
>
> Thanks, I will submit it to -stable branch.
My only reservation in submitting this to -stable is that it will in
many cases increase the default tcp_mem values, which in turn can
increase the default tcp_rmem values, and therefore the window scale.
There will be some set of people with broken firewalls who trigger that
problem for the first time by upgrading along the stable branch. While
it's not our fault, it could cause some complaints...
Thanks,
-John
next prev parent reply other threads:[~2007-04-17 19:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 21:11 TCP connection stops after high load 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 [this message]
2007-04-17 19:51 ` David Miller
2007-04-17 19:58 ` Robert Iakobashvili
2007-04-15 13:52 ` Robert Iakobashvili
-- strict thread matches above, loose matches on Subject: below --
2007-04-11 18:50 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
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
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=4625246E.2090700@psc.edu \
--to=jheffner@psc.edu \
--cc=coroberti@gmail.com \
--cc=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=moser.michael@gmail.com \
--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).