netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Neal Cardwell <ncardwell@google.com>,
	Yuchung Cheng <ycheng@google.com>, Yue Cao <ycao009@ucr.edu>
Subject: Re: [PATCH net] net: increase SOMAXCONN to 4096
Date: Thu, 31 Oct 2019 05:35:41 +0100	[thread overview]
Message-ID: <20191031043541.GA30153@1wt.eu> (raw)
In-Reply-To: <CANn89i+8FOTfq328Tv4YvhcTEn9fte6Wm4YizqubcRz=0gyiwQ@mail.gmail.com>

On Wed, Oct 30, 2019 at 08:46:26PM -0700, Eric Dumazet wrote:
> On Wed, Oct 30, 2019 at 8:36 PM Willy Tarreau <w@1wt.eu> wrote:
> > Just a quick question, I remember that when somaxconn is greater than
> > tcp_max_syn_backlog, SYN cookies are never emitted, but I think it
> > recently changed and there's no such constraint anymore. Do you
> > confirm it's no more needed, or should we also increase this latter
> > one accordingly ?
> >
> 
> There is no relationship like that.
> 
> The only place somaxconn is use is in __sys_listen() to cap the
> user-provided backlog.
> 
> somaxconn = sock_net(sock->sk)->core.sysctl_somaxconn;
> if ((unsigned int)backlog > somaxconn)
>        backlog = somaxconn;

OK, thanks for checking.

Willy

  reply	other threads:[~2019-10-31  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 16:36 [PATCH net] net: increase SOMAXCONN to 4096 Eric Dumazet
2019-10-31  3:36 ` Willy Tarreau
2019-10-31  3:46   ` Eric Dumazet
2019-10-31  4:35     ` Willy Tarreau [this message]
2019-10-31 21:02 ` David 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=20191031043541.GA30153@1wt.eu \
    --to=w@1wt.eu \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=ycao009@ucr.edu \
    --cc=ycheng@google.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).