linux-kernel - Re: [RFC PATCH] vm: align vma allocation and move the lock back into the struct

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: <be0be869-4daf-4530-b90d-6dd6c27c8736@suse.cz>
Date: Fri, 9 Aug 2024 17:09:14 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Suren Baghdasaryan <surenb@...gle.com>, Mateusz Guzik <mjguzik@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
 Liam.Howlett@...cle.com, lstoakes@...il.com, pedro.falcato@...il.com
Subject: Re: [RFC PATCH] vm: align vma allocation and move the lock back into
 the struct

On 8/9/24 05:57, Suren Baghdasaryan wrote:
> Maybe it has something to do with NUMA? The system I'm running has 2 NUMA nodes:

I kinda doubt the NUMA aspect. Whether you allocate a vma that embeds a
lock, or a vma and immediately the separate lock, it's unlikely they would
end up on different nodes so from the NUMA perspective I don't see a
difference. And if they ended up on separate nodes, it would more likely be
worse for the case of separate locks, not better.