From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Christian Brauner <brauner@kernel.org>
Cc: "Daan De Meyer" <daan.j.demeyer@gmail.com>,
"Lennart Poettering" <lennart@poettering.net>,
"Mike Yuan" <me@yhndnzj.com>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
lihongbo22@huawei.com, linux-erofs@lists.ozlabs.org,
"Gao Xiang" <xiang@kernel.org>, "Jan Kara" <jack@suse.cz>,
"Amir Goldstein" <amir73il@gmail.com>,
"Jeff Layton" <jlayton@kernel.org>,
"Hongzhen Luo" <hongzhen@linux.alibaba.com>,
"Matthew Wilcox" <willy@infradead.org>
Subject: Re: [PATCH RFC 0/4] erofs: allow page cache sharing
Date: Thu, 3 Jul 2025 20:53:34 +0800 [thread overview]
Message-ID: <43071ec1-e431-419d-b6c1-a41474f7b8bf@linux.alibaba.com> (raw)
In-Reply-To: <20250703-work-erofs-pcs-v1-0-0ce1f6be28ee@kernel.org>
On 2025/7/3 20:23, Christian Brauner wrote:
> Hey!
>
> This series is originally from Hongzhen. I'm picking it back up because
> support for page cache sharing is pretty important for container and
> service workloads that want to make use of erofs images. The main
> obstacle currently is the inability to share page cache contents between
> different erofs superblocks.
Hi Christian,
Many thanks for your effort. I do hope this feature can be
landed upstream too since as you said it's important to
container workloads.
Hongzhen had a job change recently, so he may not follow this.
It's on my own TODO list too, but it would be awesome if you
could take this!
Anyway, we could consider resending this to -fsdevel for more
discussion (I think you forgot about it ;-)). But personally
I think using anon inode mapping (vma->vm_file = anon_file)
for mmap is fine to userspace, it just needs more work to
handle edge cases like data source redirection if one sb is
gone.
Thanks,
Gao Xiang
>
> I think the mechanism that Hongzhen came up with is decent and will
> remove one final obstacle.
>
> However, I have not worked in this area in meaningful ways before so to
> an experienced page cache person this might all look like a little kid
> doodling on a piece of paper.
>
> One obvious question mark I have is around mmap. The current
> implementation mimicks what overlayfs is doing and I'm not sure that
> it's correct or even necessary to mimick overlayfs behavior here at all.
>
> Anyway, I would really appreciate the help!
next prev parent reply other threads:[~2025-07-03 12:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 12:23 [PATCH RFC 0/4] erofs: allow page cache sharing Christian Brauner
2025-07-03 12:23 ` [PATCH RFC 1/4] erofs: move `struct erofs_anon_fs_type` to super.c Christian Brauner
2025-07-03 12:23 ` [PATCH RFC 2/4] erofs: introduce page cache share feature Christian Brauner
2025-07-04 21:06 ` Gao Xiang
2025-07-05 0:54 ` Hongzhen Luo
2025-07-05 8:25 ` Amir Goldstein
2025-07-05 10:58 ` Gao Xiang
2025-07-05 12:34 ` Amir Goldstein
2025-07-05 12:53 ` Gao Xiang
2025-07-05 13:53 ` Amir Goldstein
2025-07-05 15:14 ` Gao Xiang
2025-07-05 1:09 ` Hongzhen Luo
2025-07-03 12:23 ` [PATCH RFC 3/4] erofs: apply the " Christian Brauner
2025-07-04 20:45 ` Gao Xiang
2025-07-03 12:23 ` [PATCH RFC 4/4] erofs: introduce .fadvise for page cache share Christian Brauner
2025-07-04 21:09 ` Gao Xiang
2025-07-05 1:15 ` Hongzhen Luo
2025-07-05 1:25 ` Gao Xiang
2025-07-03 12:53 ` Gao Xiang [this message]
2025-07-05 0:51 ` [PATCH RFC 0/4] erofs: allow page cache sharing Hongzhen Luo
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=43071ec1-e431-419d-b6c1-a41474f7b8bf@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=daan.j.demeyer@gmail.com \
--cc=hongzhen@linux.alibaba.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=lennart@poettering.net \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=me@yhndnzj.com \
--cc=willy@infradead.org \
--cc=xiang@kernel.org \
--cc=zbyszek@in.waw.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.