Hi David L,
On 10/14/2015 2:15 PM, Santosh Shilimkar wrote:
From: Santosh Shilimkar
To further improve the RDS connection scalabilty on massive systems
where number of sockets grows into tens of thousands of sockets, there
is a need of larger bind hashtable. Pre-allocated 8K or 16K table is
n
On 10/18/2015 6:56 PM, David Miller wrote:
From: Santosh Shilimkar
Date: Wed, 14 Oct 2015 14:15:31 -0700
From: Santosh Shilimkar
To further improve the RDS connection scalabilty on massive systems
where number of sockets grows into tens of thousands of sockets, there
is a need of larger bin
From: Santosh Shilimkar
Date: Wed, 14 Oct 2015 14:15:31 -0700
> From: Santosh Shilimkar
>
> To further improve the RDS connection scalabilty on massive systems
> where number of sockets grows into tens of thousands of sockets, there
> is a need of larger bind hashtable. Pre-allocated 8K or 16K
On 10/14/15 2:15 PM, Santosh Shilimkar wrote:
From: Santosh Shilimkar
To further improve the RDS connection scalabilty on massive systems
where number of sockets grows into tens of thousands of sockets, there
is a need of larger bind hashtable. Pre-allocated 8K or 16K table is
not very flexibl
From: Santosh Shilimkar
To further improve the RDS connection scalabilty on massive systems
where number of sockets grows into tens of thousands of sockets, there
is a need of larger bind hashtable. Pre-allocated 8K or 16K table is
not very flexible in terms of memory utilisation. The rhashtable
