From: Chris Boot <bootc@bootc.net>
To: daveflinux@aim.com
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Dropped TCP connections with 2.6.X kernel
Date: Thu, 22 Jun 2006 12:49:50 +0100 [thread overview]
Message-ID: <449A83DE.9090902@bootc.net> (raw)
In-Reply-To: <8C863E49608F8CC-184C-2F8D@FWM-D28.sysops.aol.com>
daveflinux@aim.com wrote:
> Hi,
>
> We're using a 2.6.X kernel,
> and are experiencing intermittent dropped connections when the number
> of concurrent connections exceeds ~ 1000.
>
> Does anybody have any insight into what might be happening here
> and/or troubleshooting techniques
> for isolating the problem.
> What system resources is TCP dependent on?
>
> Many thanks,
> Dave
Are all these connections handled by a single process? If so, you're
probably running into the limit of open file descriptors (1024 usually).
Look at 'help ulimit' to see how to increase the limit.
HTH,
Chris
prev parent reply other threads:[~2006-06-22 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 6:55 E1000 zero copy Heng Du
2006-06-20 8:17 ` Arjan van de Ven
[not found] ` <8C8631AA59959A1-528-3CB0@FWM-D36.sysops.aol.com>
2006-06-22 7:28 ` Dropped TCP connections with 2.6.X kernel daveflinux
2006-06-22 11:49 ` Chris Boot [this message]
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=449A83DE.9090902@bootc.net \
--to=bootc@bootc.net \
--cc=daveflinux@aim.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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