From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] socket: increase default maximum listen queue length
Date: Sun, 20 Mar 2011 12:39:21 +0100 [thread overview]
Message-ID: <20110320113921.GA3038@nuttenaction> (raw)
In-Reply-To: <1300609817.2831.56.camel@edumazet-laptop>
* Eric Dumazet | 2011-03-20 09:30:17 [+0100]:
>Hmm, real problem is not the 'maximum queue value', but the minimum one.
>
>If application says : listen(fd, 10), you are stuck.
>
>128 or 256 is way too small on some servers, where admin can tune
>in /etc/sysctl.conf :
>
>net.core.somaxconn = 8192
>net.ipv4.tcp_max_syn_backlog = 8192
>
>But application also needs to use : listen(fd, 8192)
I know Eric, I wrote the patch. ;-) The used naming goes like this:
The system limits (somaxconn & tcp_max_syn_backlog) specify a _maximum_, the
user cannot exceed this limit with listen(2). The backlog argument for listen
on the other hand specify a _minimum_. But the patch increased the default
maximum, therefore I named it in this way.
next prev parent reply other threads:[~2011-03-20 11:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 1:50 [PATCH] socket: increase default maximum listen queue length Hagen Paul Pfeifer
2011-03-20 4:41 ` David Miller
2011-03-20 11:59 ` Hagen Paul Pfeifer
2011-03-20 8:30 ` Eric Dumazet
2011-03-20 9:04 ` Rémi Denis-Courmont
2011-03-20 9:36 ` Eric Dumazet
2011-03-20 11:39 ` Hagen Paul Pfeifer [this message]
2011-03-20 11:55 ` Eric Dumazet
2011-03-20 12:14 ` Hagen Paul Pfeifer
2011-03-20 23:04 ` [PATCH 1/2] " Hagen Paul Pfeifer
2011-03-20 23:04 ` [PATCH 2/2] socket: add minimum listen queue length sysctl Hagen Paul Pfeifer
2011-03-21 7:36 ` Eric Dumazet
2011-03-20 23:09 ` [PATCH 1/2] socket: increase default maximum listen queue length David Miller
2011-03-20 23:52 ` Hagen Paul Pfeifer
2011-03-21 0:18 ` David Miller
2011-03-20 23:57 ` Hagen Paul Pfeifer
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=20110320113921.GA3038@nuttenaction \
--to=hagen@jauu.net \
--cc=eric.dumazet@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).