* [LSF/MM/BPF TOPIC] mshare - sharing page tables across processes @ 2026-02-24 2:11 anthony.yznaga 2026-02-26 0:59 ` Kalesh Singh 0 siblings, 1 reply; 3+ messages in thread From: anthony.yznaga @ 2026-02-24 2:11 UTC (permalink / raw) To: lsf-pc; +Cc: linux-mm mshare is a new form of shared memory that shares resources between processes, namely the page tables entries and VMAs of the shared objects. Advantages include reduced memory consumption through eliminating the need for duplicated PTEs in each process, reduced overhead needed to fault shared pages into multiple processes, and the ability for updates to the memory such as protection changes to be immdediately visible to all sharing processes. For some time now the proposed API has continued to evolve. With feedback from mm maintainers, a new approach using syscalls is being taken to create, attach, and deattach mshare regions and to map and manipulate the memory objects within a region. Let's discuss the current state of the API and technical challenges of managing and accomodating shared page tables in the kernel. Anthony References: https://lore.kernel.org/linux-mm/20250820010415.699353-1-anthony.yznaga@oracle.com/ https://lore.kernel.org/linux-mm/20250404021902.48863-1-anthony.yznaga@oracle.com/ ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [LSF/MM/BPF TOPIC] mshare - sharing page tables across processes 2026-02-24 2:11 [LSF/MM/BPF TOPIC] mshare - sharing page tables across processes anthony.yznaga @ 2026-02-26 0:59 ` Kalesh Singh 2026-02-26 23:48 ` Isaac Manjarres 0 siblings, 1 reply; 3+ messages in thread From: Kalesh Singh @ 2026-02-26 0:59 UTC (permalink / raw) To: anthony.yznaga Cc: lsf-pc, linux-mm, Isaac Manjarres, Suren Baghdasaryan, android-mm On Mon, Feb 23, 2026 at 6:12 PM <anthony.yznaga@oracle.com> wrote: > > mshare is a new form of shared memory that shares resources between > processes, namely the page tables entries and VMAs of the shared > objects. Advantages include reduced memory consumption through > eliminating the need for duplicated PTEs in each process, reduced > overhead needed to fault shared pages into multiple processes, and the > ability for updates to the memory such as protection changes to be > immdediately visible to all sharing processes. > > For some time now the proposed API has continued to evolve. With > feedback from mm maintainers, a new approach using syscalls is being > taken to create, attach, and deattach mshare regions and to map and > manipulate the memory objects within a region. > > Let's discuss the current state of the API and technical challenges of > managing and accomodating shared page tables in the kernel. > > Anthony > > > References: > > https://lore.kernel.org/linux-mm/20250820010415.699353-1-anthony.yznaga@oracle.com/ > https://lore.kernel.org/linux-mm/20250404021902.48863-1-anthony.yznaga@oracle.com/ Hi Anthony, I would be very interested in participating in this discussion at LSF/MM. As mentioned on the mailing list, we are currently exploring similar optimizations to deduplicate page tables for Android's Zygote process. I'd love to join the session to discuss how the proposed sharing mechanisms might align. Thanks, Kalesh > > ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [LSF/MM/BPF TOPIC] mshare - sharing page tables across processes 2026-02-26 0:59 ` Kalesh Singh @ 2026-02-26 23:48 ` Isaac Manjarres 0 siblings, 0 replies; 3+ messages in thread From: Isaac Manjarres @ 2026-02-26 23:48 UTC (permalink / raw) To: Kalesh Singh Cc: anthony.yznaga, lsf-pc, linux-mm, Suren Baghdasaryan, android-mm On Wed, Feb 25, 2026 at 04:59:32PM -0800, Kalesh Singh wrote: > On Mon, Feb 23, 2026 at 6:12 PM <anthony.yznaga@oracle.com> wrote: > > > > mshare is a new form of shared memory that shares resources between > > processes, namely the page tables entries and VMAs of the shared > > objects. Advantages include reduced memory consumption through > > eliminating the need for duplicated PTEs in each process, reduced > > overhead needed to fault shared pages into multiple processes, and the > > ability for updates to the memory such as protection changes to be > > immdediately visible to all sharing processes. > > > > For some time now the proposed API has continued to evolve. With > > feedback from mm maintainers, a new approach using syscalls is being > > taken to create, attach, and deattach mshare regions and to map and > > manipulate the memory objects within a region. > > > > Let's discuss the current state of the API and technical challenges of > > managing and accomodating shared page tables in the kernel. > > > > Anthony > > > > > > References: > > > > https://lore.kernel.org/linux-mm/20250820010415.699353-1-anthony.yznaga@oracle.com/ > > https://lore.kernel.org/linux-mm/20250404021902.48863-1-anthony.yznaga@oracle.com/ > > Hi Anthony, > > I would be very interested in participating in this discussion at LSF/MM. > > As mentioned on the mailing list, we are currently exploring similar > optimizations to deduplicate page tables for Android's Zygote process. > I'd love to join the session to discuss how the proposed sharing > mechanisms might align. > > Thanks, > Kalesh Hello Anthony, I'm also working on optimizing pagetable usage in Android with Kalesh, so I'm definitely interested in participating in this discussion as well. Thanks, Isaac ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-02-26 23:48 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2026-02-24 2:11 [LSF/MM/BPF TOPIC] mshare - sharing page tables across processes anthony.yznaga 2026-02-26 0:59 ` Kalesh Singh 2026-02-26 23:48 ` Isaac Manjarres
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox