From: David Miller <davem@davemloft.net>
To: edumazet@google.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next 0/2] tcp/dccp: better use of ephemeral ports
Date: Fri, 12 Feb 2016 05:46:06 -0500 (EST) [thread overview]
Message-ID: <20160212.054606.1764643049260890459.davem@davemloft.net> (raw)
In-Reply-To: <1455236930-17919-1-git-send-email-edumazet@google.com>
From: Eric Dumazet <edumazet@google.com>
Date: Thu, 11 Feb 2016 16:28:48 -0800
> Big servers have bloated bind table, making very hard to succeed
> ephemeral port allocations, without special containers/namespace tricks.
>
> This patch series extends the strategy added in commit 07f4c90062f8
> ("tcp/dccp: try to not exhaust ip_local_port_range in connect()").
>
> Since ports used by connect() are much likely to be shared among them,
> we give a hint to both bind() and connect() to keep the crowds separated
> if possible.
>
> Of course, if on a specific host an application needs to allocate ~30000
> ports using bind(), it will still be able to do so. Same for ~30000 connect()
> to a unique 2-tuple (dst addr, dst port)
>
> New implemetation is also more friendly to softirqs and reschedules.
>
> v2: rebase after TCP SO_REUSEPORT changes
Series applied, thanks.
prev parent reply other threads:[~2016-02-12 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 0:28 [PATCH v2 net-next 0/2] tcp/dccp: better use of ephemeral ports Eric Dumazet
2016-02-12 0:28 ` [PATCH v2 net-next 1/2] tcp/dccp: better use of ephemeral ports in connect() Eric Dumazet
2016-02-12 0:28 ` [PATCH v2 net-next 2/2] tcp/dccp: better use of ephemeral ports in bind() Eric Dumazet
2016-02-12 10:46 ` David 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=20160212.054606.1764643049260890459.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--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).