From: Ben Greear <greearb@candelatech.com>
To: Luke Hutchison <luke.hutch@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Networking hangs when too many parallel requests are made at once
Date: Tue, 09 Nov 2010 11:16:48 -0800 [thread overview]
Message-ID: <4CD99E20.4060307@candelatech.com> (raw)
In-Reply-To: <AANLkTinRo_ozWFCYYqanOh0YrTJ6+KadutG2j7T726dY@mail.gmail.com>
On 11/09/2010 11:04 AM, Luke Hutchison wrote:
> On Tue, Nov 9, 2010 at 1:30 PM, Luke Hutchison<luke.hutch@gmail.com> wrote:
>> Since around Linux kernel 2.6.33 or so (but maybe as early as
>> 2.6.31, not sure exactly what version), when restoring a crashed or
>> closed browser session of either Firefox or Chrome where lots of tabs
>> (say 10-40) open simultaneously, the networking stack is brought to
>> its knees -- most or all the tabs eventually time out without data, or
>> a few tabs might get some data and then display a partial web page.
Have you been able to reproduce this on any other machine? I suspect
it might be an issue with your specific NIC or other hardware.
At the least, it's not a general problem with opening lots
of TCP connections, as we routinely test with thousands...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-11-09 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 18:30 Networking hangs when too many parallel requests are made at once Luke Hutchison
2010-11-09 19:04 ` Luke Hutchison
2010-11-09 19:16 ` Ben Greear [this message]
2010-11-09 20:27 ` Luke Hutchison
2010-11-09 20:35 ` Ben Greear
2010-11-09 21:17 ` Luke Hutchison
2010-11-09 22:14 ` Ben Greear
2010-11-09 22:20 ` Luke Hutchison
2010-11-09 22:29 ` Ben Greear
2010-11-09 22:38 ` Luke Hutchison
2010-11-09 22:49 ` Ben Greear
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=4CD99E20.4060307@candelatech.com \
--to=greearb@candelatech.com \
--cc=luke.hutch@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).