On Wed, 2015-05-27 at 13:31 -0400, David Miller wrote:
> Looks fine, applied, thanks Eric.
>
> Arguably, we might want to emit a warning if the user sets the port
> range sysctl non-even. But that's up to you.
Right, I guess we can do that. I'll send a followup patch.
Thanks !
--
To unsubs
From: Eric Dumazet
Date: Sun, 24 May 2015 14:49:35 -0700
> From: Eric Dumazet
>
> A long standing problem on busy servers is the tiny available TCP port
> range (/proc/sys/net/ipv4/ip_local_port_range) and the default
> sequential allocation of source ports in connect() system call.
>
> If a h
From: Eric Dumazet
A long standing problem on busy servers is the tiny available TCP port
range (/proc/sys/net/ipv4/ip_local_port_range) and the default
sequential allocation of source ports in connect() system call.
If a host is having a lot of active TCP sessions, chances are
very high that al
