From: "David S. Miller" <davem@redhat.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: ahu@ds9a.nl, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [DOCUMENTATION PATCH] Missing net sysctls, some fixed, rest flagged
Date: Wed, 16 Jun 2004 11:15:31 -0700 [thread overview]
Message-ID: <20040616111531.6047bb40.davem@redhat.com> (raw)
In-Reply-To: <40D006BF.7020002@cosmosbay.com>
On Wed, 16 Jun 2004 10:37:19 +0200
Eric Dumazet <dada1@cosmosbay.com> wrote:
> I dont agree with the 'TCP' word here : listen() system call is not tied
> with TCP, isn't it ?
> I would suggest :
>
> +somaxconn - INTEGER
> + Limit of socket listen() backlog, known in userspace as SOMAXCONN.
> + Defaults to 128. See also tcp_max_syn_backlog for additional tuning for TCP sockets.
> +
Works for me. Applied.
prev parent reply other threads:[~2004-06-16 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 17:52 [DOCUMENTATION PATCH] Missing net sysctls, some fixed, rest flagged bert hubert
2004-06-16 3:19 ` David S. Miller
2004-06-16 8:37 ` Eric Dumazet
2004-06-16 18:15 ` David S. Miller [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=20040616111531.6047bb40.davem@redhat.com \
--to=davem@redhat.com \
--cc=ahu@ds9a.nl \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--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).