From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Hongbo Li <lihongbo22@huawei.com>,
chao@kernel.org, brauner@kernel.org, djwong@kernel.org,
amir73il@gmail.com, joannelkoong@gmail.com
Cc: linux-fsdevel@vger.kernel.org, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 6/9] erofs: introduce the page cache share feature
Date: Mon, 17 Nov 2025 11:06:21 +0800 [thread overview]
Message-ID: <ac1b5431-e71f-430d-8309-8d007dc449b9@linux.alibaba.com> (raw)
In-Reply-To: <20251114095516.207555-7-lihongbo22@huawei.com>
On 2025/11/14 17:55, 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
> deduplicated inode and use its page cache as shared. Reads for files
> with identical content will ultimately be routed to the page cache of
> the deduplicated inode. In this way, a single page cache satisfies
> multiple read requests for different files with the same contents.
>
> Signed-off-by: Hongzhen Luo <hongzhen@linux.alibaba.com>
> Signed-off-by: Hongbo Li <lihongbo22@huawei.com>
> ---
...
> +
> +static int erofs_ishare_file_open(struct inode *inode, struct file *file)
> +{
> + struct file *realfile;
> + struct inode *dedup;
> +
> + dedup = EROFS_I(inode)->ishare;
> + if (!dedup)
> + return -EINVAL;
> +
> + realfile = alloc_file_pseudo(dedup, erofs_ishare_mnt, "erofs_ishare_file",
> + O_RDONLY, &erofs_file_fops);
> + if (IS_ERR(realfile))
> + return PTR_ERR(realfile);
> +
> + file_ra_state_init(&realfile->f_ra, file->f_mapping);
> + realfile->private_data = EROFS_I(inode);
> + file->private_data = realfile;
> + return 0;
Again, as Amir mentioned before, it should be converted to use (at least)
some of backing file interfaces, please see:
file_user_path() and file_user_inode() in include/linux/fs.h
Or are you sure /proc/<pid>/maps is shown as expected?
Thanks,
Gao Xiang
next prev parent reply other threads:[~2025-11-17 3:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 9:55 [PATCH v8 0/9] erofs: inode " Hongbo Li
2025-11-14 9:55 ` [PATCH v8 1/9] iomap: stash iomap read ctx in the private field of iomap_iter Hongbo Li
2025-11-16 11:53 ` Gao Xiang
2025-11-16 11:54 ` Gao Xiang
2025-11-14 9:55 ` [PATCH v8 2/9] erofs: hold read context in iomap_iter if needed Hongbo Li
2025-11-16 12:01 ` Gao Xiang
2025-11-17 1:45 ` Hongbo Li
2025-11-14 9:55 ` [PATCH v8 3/9] erofs: move `struct erofs_anon_fs_type` to super.c Hongbo Li
2025-11-16 12:02 ` Gao Xiang
2025-11-14 9:55 ` [PATCH v8 4/9] erofs: support user-defined fingerprint name Hongbo Li
2025-11-17 2:54 ` Gao Xiang
2025-11-17 7:41 ` Hongbo Li
2025-11-14 9:55 ` [PATCH v8 5/9] erofs: support domain-specific page cache share Hongbo Li
2025-11-14 9:55 ` [PATCH v8 6/9] erofs: introduce the page cache share feature Hongbo Li
2025-11-17 3:06 ` Gao Xiang [this message]
2025-11-17 3:14 ` Hongbo Li
2025-11-17 3:18 ` Hongbo Li
2025-11-17 3:30 ` Gao Xiang
2025-11-14 9:55 ` [PATCH v8 7/9] erofs: support unencoded inodes for page cache share Hongbo Li
2025-11-17 3:44 ` Gao Xiang
2025-11-14 9:55 ` [PATCH v8 8/9] erofs: support compressed " Hongbo Li
2025-11-14 9:55 ` [PATCH v8 9/9] erofs: implement .fadvise " Hongbo Li
2025-11-17 3:48 ` 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=ac1b5431-e71f-430d-8309-8d007dc449b9@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=joannelkoong@gmail.com \
--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
all inboxes | Powered by JetHome®