linux-kernel - Re: [PATCH] Increase default MLOCK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <CFRG8CM6QUPN.1Z75SA6XN02W1@taiga>
Date:   Tue, 16 Nov 2021 20:25:33 +0100
From:   "Drew DeVault" <sir@...wn.com>
To:     "Vito Caputo" <vcaputo@...garu.com>, "Jens Axboe" <axboe@...nel.dk>
Cc:     "Matthew Wilcox" <willy@...radead.org>,
        "Andrew Morton" <akpm@...ux-foundation.org>,
        "Ammar Faizi" <ammarfaizi2@...weeb.org>,
        <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 Tue Nov 16, 2021 at 8:21 PM CET, Vito Caputo wrote:
> Considering a single fullscreen 32bpp 4K-resolution framebuffer is
> ~32MiB, I'm not convinced this is really correct in nearly 2022.

Can you name a practical use-case where you'll be doing I/O with
uncompressed 4K framebuffers? The kind of I/O which is supported by
io_uring, to be specific, not, say, handing it off to libdrm.