Re: [PATCH 4.15-rc8] net/core: Increase default optmem_max limit

2018-01-16 Thread David Miller
From: Björn 'besser82' Esser Date: Tue, 16 Jan 2018 00:59:11 +0100 > @@ -316,7 +316,7 @@ __u32 sysctl_wmem_default __read_mostly > __u32 sysctl_rmem_default __read_mostly = SK_RMEM_MAX; > > /* Maximal > space eaten by iovec or ancillary data plus some space */ This patch is corrupted by you

Re: [PATCH 4.15-rc8] net/core: Increase default optmem_max limit

2018-01-15 Thread Björn 'besser82' Esser
With the new Linux Kernel Crypto API User Space Interface and its underlying socket interface, the current default value for `net.core.optmem_max` can be exhausted pretty quick. On 32 bit systems it is not even enough for sending 16 IOVECs at once to the socket interface. To provide consumers of t

[PATCH 4.15-rc8] net/core: Increase default optmem_max limit

2018-01-15 Thread Björn 'besser82' Esser
With the new Linux Kernel Crypto API User Space Interface and its underlying socket interface, the current default value for `net.core.optmem_max` can be exhausted pretty quick. On 32 bit systems it is not even enough for sending 16 IOVECs at once to the socket interface. To provide consumers of t

[PATCH 4.15-rc8] net/core: Increase default optmem_max limit

2018-01-15 Thread Björn 'besser82' Esser
With the new Linux Kernel Crypto API User Space Interface and its underlying socket interface, the current default value for `net.core.optmem_max` can be exhausted pretty quick. On 32 bit systems it is not even enough for sending 16 IOVECs at once to the socket interface. To provide consumers of t