From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: davidm@hpl.hp.com, davidm@napali.hpl.hp.com, netdev@oss.sgi.com
Subject: Re: SOMAXCONN too low
Date: Wed, 29 Oct 2003 20:47:07 +0100 [thread overview]
Message-ID: <20031029204707.67f9a2e1.ak@suse.de> (raw)
In-Reply-To: <20031029105809.0a1f27a1.davem@redhat.com>
On Wed, 29 Oct 2003 10:58:09 -0800
"David S. Miller" <davem@redhat.com> wrote:
> On Tue, 28 Oct 2003 22:58:00 -0800
> David Mosberger <davidm@napali.hpl.hp.com> wrote:
>
> > You obviously want some control over how big the listen queue can
> > grow, but it seems to me that a sysctl would be in place. I found
> > this patch to do that, but no reaction to it:
> >
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0205.0/1287.html
>
> I think I'm going to apply this patch.
>
> People can then set the limit to what they want, the default
> stays at 128, and the SOMAXCONN define itself does not change.
>
> Ok David?
Can I respectfully ask to name the sysctl net/core/somaxconn ?
That is the name used in the SuSE/UL kernels and has been shipping for some time
and already has a big user base, and there is no reason to break compatibility
for them.
Thanks,
-Andi
next prev parent reply other threads:[~2003-10-29 19:47 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
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 [this message]
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=20031029204707.67f9a2e1.ak@suse.de \
--to=ak@suse.de \
--cc=davem@redhat.com \
--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).