From: "Drew DeVault" <[email protected]>
To: "Vito Caputo" <[email protected]>
Cc: <[email protected]>
Subject: Re: Is IORING_REGISTER_BUFFERS useful given the current default RLIMIT_MLOCK?
Date: Tue, 26 Oct 2021 09:12:02 +0200 [thread overview]
Message-ID: <CF95HABUTLQT.3S7V7X41CM2X2@taiga> (raw)
In-Reply-To: <[email protected]>
On Mon Oct 25, 2021 at 5:42 PM CEST, Vito Caputo wrote:
> If not for the gpg precedent cited, I'd say it's obviously
> distribution-specific defaults choice territory when it's as simple as
> what's preset in /etc/security/limits.conf.
>
> Systemd has also been getting its hands a bit dirty in the area of
> bumping resource limits, which I'm not sure how I feel about. But it
> does illustrate how downstream is perfectly capable of managing these
> limits on behalf of users.
Most distros don't touch this default value as far as I'm aware, and the
buck, as it were, stops with the kernel. I would prefer to bikeshed this
once rather than N times where N is the number of Linux distributions.
Accordingly, should any of the distros prefer the original value, or
another value, they're entirely able to configure new defaults according
to their preferences.
prev parent reply other threads:[~2021-10-26 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 13:58 Is IORING_REGISTER_BUFFERS useful given the current default RLIMIT_MLOCK? Drew DeVault
2021-10-25 15:42 ` Vito Caputo
2021-10-26 7:12 ` Drew DeVault [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=CF95HABUTLQT.3S7V7X41CM2X2@taiga \
[email protected] \
[email protected] \
[email protected] \
/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