[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ec24ff4e-8413-914c-7cdf-203a7a5f0586@kernel.dk>
Date: Wed, 17 Nov 2021 16:17:26 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Johannes Weiner <hannes@...xchg.org>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Ammar Faizi <ammarfaizi2@...weeb.org>,
Drew DeVault <sir@...wn.com>, linux-kernel@...r.kernel.org,
linux-api@...r.kernel.org,
io_uring Mailing List <io-uring@...r.kernel.org>,
Pavel Begunkov <asml.silence@...il.com>, linux-mm@...ck.org
Subject: Re: [PATCH] Increase default MLOCK_LIMIT to 8 MiB
On 11/17/21 3:26 PM, Johannes Weiner wrote:
>> Link: https://lkml.kernel.org/r/20211028080813.15966-1-sir@cmpwn.com
>> Signed-off-by: Drew DeVault <sir@...wn.com>
>> Acked-by: Jens Axboe <axboe@...nel.dk>
>> Acked-by: Cyril Hrubis <chrubis@...e.cz>
>> Cc: Pavel Begunkov <asml.silence@...il.com>
>> Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
>
> Acked-by: Johannes Weiner <hannes@...xchg.org>
>
> As per above, I think basing it off of RAM size would be better, but
> this increase is overdue given all the new users beyond mlock(), and
> 8M is much better than the current value.
That's basically my reasoning too. Let's just get something going that
will at least unblock some valid use cases, and not get bogged down with
aiming for perfection. The latter can happen in parallel, but it should
not hold it up imho.
--
Jens Axboe
Powered by blists - more mailing lists