From: Andi Kleen <ak@suse.de>
To: Tim Hockin <thockin@sun.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SOMAXCONN - bump up or sysctl?
Date: 13 Jul 2001 09:35:49 +0200 [thread overview]
Message-ID: <oupn169cmcq.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <3B4E7EA1.F904DC43@sun.com.suse.lists.linux.kernel>
In-Reply-To: Tim Hockin's message of "13 Jul 2001 07:09:53 +0200"
Tim Hockin <thockin@sun.com> writes:
> hey all,
>
> We have a request to bump up SOMAXCONN. Are there are repurcussions to
> doing so? Would it be better to make it a sysctl?
Have you checked if the requester is not satisfied with an increase
of /proc/sys/net/ipv4/tcp_max_syn_backlog? If they "know" from 2.0
that they want a SOMAXCONN increase then that's very likely the case.
In 2.2+ SOMAXCONN only applies to established sockets waiting to get
accept()ed; and when you have 128 established sockets that don't get served
by accept you have a big problem.
SYN-RECV sockets are a completely different thing and they are tuned
by the first sysctl and some other heuristics in 2.4.
You can also turn on syncookies there to handle syn-recv load spikes.
-Andi
next parent reply other threads:[~2001-07-13 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B4E7EA1.F904DC43@sun.com.suse.lists.linux.kernel>
2001-07-13 7:35 ` Andi Kleen [this message]
2001-07-13 4:52 SOMAXCONN - bump up or sysctl? Tim Hockin
2001-07-13 8:14 ` David S. Miller
2001-07-13 10:44 ` Alan Cox
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=oupn169cmcq.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.