From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: hch@lst.de, djwong@kernel.org, amir73il@gmail.com,
linux-fsdevel@vger.kernel.org, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Chao Yu <chao@kernel.org>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH v17 06/10] erofs: introduce the page cache share feature
Date: Fri, 23 Jan 2026 00:34:04 +0800 [thread overview]
Message-ID: <c437672e-d0aa-49e7-b033-be5133cd18a3@linux.alibaba.com> (raw)
In-Reply-To: <20260122153406.660073-7-lihongbo22@huawei.com>
On 2026/1/22 23:34, Hongbo Li wrote:
> From: Hongzhen Luo <hongzhen@linux.alibaba.com>
>
> Currently, reading files with different paths (or names) but the same
> content will consume multiple copies of the page cache, even if the
> content of these page caches is the same. For example, reading
> identical files (e.g., *.so files) from two different minor versions of
> container images will cost multiple copies of the same page cache,
> since different containers have different mount points. Therefore,
> sharing the page cache for files with the same content can save memory.
>
> This introduces the page cache share feature in erofs. It allocate a
> shared inode and use its page cache as shared. Reads for files
> with identical content will ultimately be routed to the page cache of
> the shared inode. In this way, a single page cache satisfies
> multiple read requests for different files with the same contents.
>
> We introduce new mount option `inode_share` to enable the page
> sharing mode during mounting. This option is used in conjunction
> with `domain_id` to share the page cache within the same trusted
> domain.
>
> Signed-off-by: Hongzhen Luo <hongzhen@linux.alibaba.com>
> Signed-off-by: Hongbo Li <lihongbo22@huawei.com>
Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Thanks,
Gao Xiang
next prev parent reply other threads:[~2026-01-22 16:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 15:33 [PATCH v17 00/10] erofs: Introduce page cache sharing feature Hongbo Li
2026-01-22 15:33 ` [PATCH v17 01/10] fs: Export alloc_empty_backing_file Hongbo Li
2026-01-22 15:33 ` [PATCH v17 02/10] erofs: decouple `struct erofs_anon_fs_type` Hongbo Li
2026-01-22 15:33 ` [PATCH v17 03/10] erofs: support user-defined fingerprint name Hongbo Li
2026-01-22 15:34 ` [PATCH v17 04/10] erofs: add erofs_inode_set_aops helper to set the aops Hongbo Li
2026-01-22 16:28 ` Gao Xiang
2026-01-22 15:34 ` [PATCH v17 05/10] erofs: using domain_id in the safer way Hongbo Li
2026-01-22 16:32 ` Gao Xiang
2026-01-22 15:34 ` [PATCH v17 06/10] erofs: introduce the page cache share feature Hongbo Li
2026-01-22 16:34 ` Gao Xiang [this message]
2026-01-22 15:34 ` [PATCH v17 07/10] erofs: pass inode to trace_erofs_read_folio Hongbo Li
2026-01-22 16:37 ` Gao Xiang
2026-01-22 15:34 ` [PATCH v17 08/10] erofs: support unencoded inodes for page cache share Hongbo Li
2026-01-22 16:39 ` Gao Xiang
2026-01-22 15:34 ` [PATCH v17 09/10] erofs: support compressed " Hongbo Li
2026-01-22 15:34 ` [PATCH v17 10/10] erofs: implement .fadvise " Hongbo Li
2026-01-22 16:40 ` Gao Xiang
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=c437672e-d0aa-49e7-b033-be5133cd18a3@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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