aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2022-06-04 06:02:53 -0600
committerJens Axboe <axboe@kernel.dk>2022-06-04 06:02:53 -0600
commitd4a41927e1184745f318fafef828d92060ba0d5b (patch)
tree25b011c567ed08e642e7596367fa2f995d802ecd
parentfebf522af0e83938d7c4a0d553b2631c7ba1178f (diff)
downloadliburing-d4a41927e1184745f318fafef828d92060ba0d5b.tar.gz
README: clarify when RLIMIT_MEMLOCK is still used
For newer kernels, the rings themselves are not accounted via RLIMIT_MEMLOCK, but registered buffers still are. Signed-off-by: Jens Axboe <axboe@kernel.dk>
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
diff --git a/README b/README
index afd14b0..80d2b3d 100644
--- a/README
+++ b/README
@@ -36,7 +36,7 @@ into detail on how to bump the limit on various systems is beyond the scope
of this little blurb, but check /etc/security/limits.conf for user specific
settings, or /etc/systemd/user.conf and /etc/systemd/system.conf for systemd
setups. This affects 5.11 and earlier, new kernels are less dependent
-on RLIMIT_MEMLOCK.
+on RLIMIT_MEMLOCK as it is only used for registering buffers.
Regressions tests