From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
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)
Message-ID: <20160212.054606.1764643049260890459.davem@davemloft.net>
References: <1455236930-17919-1-git-send-email-edumazet@google.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
To: edumazet@google.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([149.20.54.216]:35637 "EHLO
	shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751102AbcBLKqN (ORCPT
	<rfc822;netdev@vger.kernel.org>); Fri, 12 Feb 2016 05:46:13 -0500
In-Reply-To: <1455236930-17919-1-git-send-email-edumazet@google.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

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.