On Mon, Oct 25, 2021 at 03:58:33PM +0200, Drew DeVault wrote: > The current default for RLIMIT_MLOCK is set to 64 KiB. This is not much! > This limit was set to this value in 2008 at the request of GnuPG. > > I understand that the main audience of io_uring is high-performance > servers and such, where configuring the rlimits appropriately is not a > particularly burdensome ask. However, this dramatically limits the > utility of IORING_REGISTER_BUFFERS in the end-user software use-case, > almost such that it's entirely pointless *without* raising the mlock > rlimit. > > I wonder if we can/should make a case for raising the default rlimit to > something more useful for $CURRENTYEAR? 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. Regards, Vito Caputo