linux-kernel - Re: Is it possible to implement the per-node page cache for programs/libraries?

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]

Date:   Wed, 1 Sep 2021 18:13:56 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Barry Song <21cnbao@...il.com>
Cc:     Matthew Wilcox <willy@...radead.org>,
        Huang Shijie <shijie@...amperecomputing.com>,
        Shijie Huang <shijie@...eremail.onmicrosoft.com>,
        Al Viro <viro@...iv.linux.org.uk>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux-MM <linux-mm@...ck.org>,
        Barry Song <song.bao.hua@...ilicon.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Frank Wang <zwang@...erecomputing.com>
Subject: Re: Is it possible to implement the per-node page cache for programs/libraries?

On Wed, Sep 1, 2021 at 5:15 PM Barry Song <21cnbao@...il.com> wrote:
>
> In case we are running mysql on a machine with 128 cores
> (4numa, 32cores in each numa), how will the reflink help the only
> mysql process to leverage its local libc copy?

That's a fundamentally harder problem anyway, and for the foreseeable
future you should expect the answer to that be "Not a way in hell".

Because it's not about "local libc copies" at that point any more,
it's about "a single process only has a single page table".

So a single process will have a particular virtual address mapped to
*one* physical page. And no, it doesn't matter how many threads you
have. What makes them threads - not processes - is that they share the
same VM image.

So the only way you will have local NUMA copies is if you
 (a) run multiple processes
 (b) bind each process to a particular NUMA node
 (c) do something special to then have per-node mappings

That "(c)" is what is up for discussion, whether it be with various
user mode hacks, or the "NUMA COW" thing, or whatever.

But (a) and (b) are basically required.

               Linus