From: "Björn 'besser82' Esser" <besser82@fedoraproject.org>
To: David Miller <davem@davemloft.net>
Cc: waltje@uWalt.NL.Mugnet.ORG, flla@stud.uni-sb.de,
A.Cox@swansea.ac.uk, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, trivial@kernel.org, labbott@redhat.com,
zbyszek@in.waw.pl, Stephan Mueller <smueller@chronox.de>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v2] net/core: Increase default optmem_max limit
Date: Tue, 16 Jan 2018 18:16:43 +0100 [thread overview]
Message-ID: <02fd8c825b9d77bfc6c7f6318cdddb85fb295ec6.camel@fedoraproject.org> (raw)
In-Reply-To: <6842b4da93e5fb588b2e64550a20089e9f60fad6.camel@fedoraproject.org>
With the new Linux Kernel Crypto API User Space Interface
and its underlying AF_ALG socket, the current default value
for `net.core.optmem_max` can be exhausted pretty quick when
using asynchronous IO; on 32 bit systems it is not even enough
for sending about 10 IOVECs at once to the socket interface.
To provide consumers of this new user space interface a well
sufficient and reasonable maximum ancillary buffer size per
socket by default, the limit is increased to four times of
the previous setting:
* 32 bit systems: from 10240 bytes to 40960 bytes
* 64 bit systems: from 20480 bytes to 81920 bytes
This allows for sending 32/64 (32/64 bit) parallel IOVECs at
once to the socket interface, which should be enough for use
in real world applications.
Signed-off-by: Björn Esser <besser82@fedoraproject.org>
---
net/core/sock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/core/sock.c b/net/core/sock.c
index c0b5b2f17412..de00c571c933 100644
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -316,7 +316,7 @@ __u32 sysctl_wmem_default __read_mostly = SK_WMEM_MAX;
__u32 sysctl_rmem_default __read_mostly = SK_RMEM_MAX;
/* Maximal space eaten by iovec or ancillary data plus some space */
-int sysctl_optmem_max __read_mostly = sizeof(unsigned long)*(2*UIO_MAXIOV+512);
+int sysctl_optmem_max __read_mostly = sizeof(unsigned long)*4*(2*UIO_MAXIOV+512);
EXPORT_SYMBOL(sysctl_optmem_max);
int sysctl_tstamp_allow_data __read_mostly = 1;
next prev parent reply other threads:[~2018-01-16 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 23:59 [PATCH 4.15-rc8] net/core: Increase default optmem_max limit Björn 'besser82' Esser
2018-01-16 0:16 ` Björn 'besser82' Esser
2018-01-16 14:30 ` David Miller
2018-01-16 17:13 ` [PATCH v2] " Björn 'besser82' Esser
2018-01-16 17:16 ` Björn 'besser82' Esser [this message]
2018-01-16 18:11 ` Stephan Mueller
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=02fd8c825b9d77bfc6c7f6318cdddb85fb295ec6.camel@fedoraproject.org \
--to=besser82@fedoraproject.org \
--cc=A.Cox@swansea.ac.uk \
--cc=davem@davemloft.net \
--cc=flla@stud.uni-sb.de \
--cc=labbott@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=smueller@chronox.de \
--cc=trivial@kernel.org \
--cc=waltje@uWalt.NL.Mugnet.ORG \
--cc=zbyszek@in.waw.pl \
/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).