From: Andi Kleen <ak@suse.de>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, netdev@oss.sgi.com
Subject: Re: SOMAXCONN too low
Date: Wed, 29 Oct 2003 13:33:15 +0100 [thread overview]
Message-ID: <20031029133315.5638f842.ak@suse.de> (raw)
In-Reply-To: <200310290658.h9T6w04k015302@napali.hpl.hp.com>
On Tue, 28 Oct 2003 22:58:00 -0800
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> Also, it appears that current SuSE kernels do indeed have a
> net.core.somaxconn sysctl to let a sysadmin choose a larger SOMAXCONN
> value.
Yes I did that patch some time ago for some server who needed it. If there is interest
I can submit it for 2.6. But I'm not sure it fits the "important bug fixes only" rule.
Another alternative would be to make it a fraction of the listen() argument per socket
(e.g. min(tcp_max_syn_backlog,min(128,10%*listenarg))) to allow the application
to easily change it.
-Andi
next prev parent reply other threads:[~2003-10-29 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 6:58 SOMAXCONN too low David Mosberger
2003-10-29 12:33 ` Andi Kleen [this message]
2003-10-29 17:13 ` David Mosberger
2003-10-29 17:22 ` David S. Miller
2003-10-29 18:08 ` David Mosberger
2003-10-29 18:43 ` David S. Miller
2003-10-29 18:58 ` David S. Miller
2003-10-29 19:15 ` David Mosberger
2003-10-29 19:47 ` Andi Kleen
2003-10-29 19:45 ` David S. Miller
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=20031029133315.5638f842.ak@suse.de \
--to=ak@suse.de \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=netdev@oss.sgi.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 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).