From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Jan Kara <jack@suse.cz>, David Hildenbrand <david@redhat.com>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [LSF/MM/BPF TOPIC] The future of anon_vma
Date: Thu, 13 Mar 2025 18:41:40 +0000 [thread overview]
Message-ID: <9699c035-e629-447f-b237-c8fb5c1e34df@lucifer.local> (raw)
In-Reply-To: <c87f41ff-a49c-4476-8153-37ff667f47b9@lucifer.local>
As with the ongoing evolution of this, as previously discussed, the focus
has settled on merging of anonymous VMAs and improving this mergeability.
I have an RFC series (not upstreamed yet, but should be by LSF) which
optionally permits improved anonymous mapping mergeability by passing a
flag to mremap().
In this topic I'd like to discuss that, anon_vma in general motivations for
it, why it's hard, etc.
This dovetails with the original proposal - bit is a less ambitious, more
short-term 'how can we improve the situation' kind of thing. Maybe next
year there can be more :)
My slides are at ~31 right now, so I wonder whether I could have an hour
slot for this? As I'd also like to have some discussion of course! :)
Thanks!
next prev parent reply other threads:[~2025-03-13 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 22:23 Lorenzo Stoakes
2025-01-09 10:21 ` [Lsf-pc] " Jan Kara
2025-01-09 12:33 ` Lorenzo Stoakes
2025-01-13 11:21 ` Jan Kara
2025-02-22 18:26 ` Lorenzo Stoakes
2025-03-08 18:15 ` Lorenzo Stoakes
2025-02-23 8:08 ` Dev Jain
2025-02-23 8:21 ` Lorenzo Stoakes
2025-03-13 18:41 ` Lorenzo Stoakes [this message]
2025-03-22 7:45 ` Lorenzo Stoakes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9699c035-e629-447f-b237-c8fb5c1e34df@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=david@redhat.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox