From: Jan Kara <jack@suse.cz>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] The future of anon_vma
Date: Thu, 9 Jan 2025 11:21:02 +0100 [thread overview]
Message-ID: <zh2hu4fzaqrhw5qdbpcspcsvmnczjo7v5q4b65uq7eaz7exanz@ihsk5oa5njfn> (raw)
In-Reply-To: <c87f41ff-a49c-4476-8153-37ff667f47b9@lucifer.local>
Hi!
On Wed 08-01-25 22:23:16, Lorenzo Stoakes via Lsf-pc wrote:
> A future where we unify anonymous and file-backed memory mappings would be
> one in which a reflinks were implemented at a general level rather than, as
> they are now, implemented individually within file systems.
>
> I'd like to discuss how feasible doing so might be, whether this is a sane
> line of thought at all, and how a roadmap for working towards the
> elimination of anon_vma as it stands might look.
As you can imagine this has been discussed in the past and some folks are
very interested in saving page cache memory for some heavily reflinked
container setups or for various FUSE filesystems. So if someone manages to
come up with a feasible design, the usecases are there. I think reading
e.g. [1] and comments below it is a good preparation for the session to get
some idea what challenges are there :).
Honza
[1] https://lwn.net/Articles/717950/
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2025-01-09 10:21 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 ` Jan Kara [this message]
2025-01-09 12:33 ` [Lsf-pc] " 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
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=zh2hu4fzaqrhw5qdbpcspcsvmnczjo7v5q4b65uq7eaz7exanz@ihsk5oa5njfn \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lsf-pc@lists.linux-foundation.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