From: Stephan Mueller <smueller@chronox.de>
To: "Björn 'besser82' Esser" <besser82@fedoraproject.org>
Cc: David Miller <davem@davemloft.net>,
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, linux-crypto@vger.kernel.org
Subject: Re: [PATCH v2] net/core: Increase default optmem_max limit
Date: Tue, 16 Jan 2018 19:11:37 +0100 [thread overview]
Message-ID: <3580634.dJdEtStb76@tauon.chronox.de> (raw)
In-Reply-To: <02fd8c825b9d77bfc6c7f6318cdddb85fb295ec6.camel@fedoraproject.org>
Am Dienstag, 16. Januar 2018, 18:16:43 CET schrieb Björn 'besser82' Esser:
Hi Björn,
> 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>
Considering NR_FILE defining the default maximum number of file descriptors,
at max 335 MB of RAM (32 bit) or 670 MB (64 bit) could be allocated which I
would assume to be ok in current systems.
Reviewed-by: Stephan Mueller <smueller@chronox.de>
Ciao
Stephan
prev parent reply other threads:[~2018-01-16 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 23:59 [PATCH 4.15-rc8] " 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
2018-01-16 18:11 ` Stephan Mueller [this message]
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=3580634.dJdEtStb76@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=A.Cox@swansea.ac.uk \
--cc=besser82@fedoraproject.org \
--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=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
all inboxes | Powered by JetHome®