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, hch@lst.de
Cc: linux-fsdevel@vger.kernel.org, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 02/10] erofs: hold read context in iomap_iter if needed
Date: Tue, 23 Dec 2025 10:32:46 +0800 [thread overview]
Message-ID: <65cf64e7-c395-4508-9bac-5a8dc08e8f3c@linux.alibaba.com> (raw)
In-Reply-To: <20251223015618.485626-3-lihongbo22@huawei.com>
On 2025/12/23 09:56, Hongbo Li wrote:
> Introduce `struct erofs_iomap_iter_ctx` to hold both `struct page *`
> and `void *base`, avoiding bogus use of `kmap_to_page()` in
> `erofs_iomap_end()`.
>
> With this change, fiemap and bmap no longer need to read inline data.
>
> Additionally, the upcoming page cache sharing mechanism requires
> passing the backing inode pointer to `erofs_iomap_{begin,end}()`, as
> I/O accesses must apply to backing inodes rather than anon inodes.
>
> 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:[~2025-12-23 2:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 1:56 [PATCH v10 00/10] erofs: Introduce page cache sharing feature Hongbo Li
2025-12-23 1:56 ` [PATCH v10 01/10] iomap: stash iomap read ctx in the private field of iomap_iter Hongbo Li
2025-12-23 2:32 ` Gao Xiang
2025-12-23 1:56 ` [PATCH v10 02/10] erofs: hold read context in iomap_iter if needed Hongbo Li
2025-12-23 2:32 ` Gao Xiang [this message]
2025-12-23 1:56 ` [PATCH v10 03/10] fs: Export alloc_empty_backing_file Hongbo Li
2025-12-23 8:31 ` Gao Xiang
2025-12-23 12:40 ` Amir Goldstein
2025-12-23 1:56 ` [PATCH v10 04/10] erofs: move `struct erofs_anon_fs_type` to super.c Hongbo Li
2025-12-23 8:30 ` Gao Xiang
2025-12-23 9:28 ` Hongbo Li
2025-12-23 1:56 ` [PATCH v10 05/10] erofs: support user-defined fingerprint name Hongbo Li
2025-12-23 7:22 ` Gao Xiang
2025-12-23 1:56 ` [PATCH v10 06/10] erofs: support domain-specific page cache share Hongbo Li
2025-12-23 7:25 ` Gao Xiang
2025-12-23 1:56 ` [PATCH v10 07/10] erofs: introduce the page cache share feature Hongbo Li
2025-12-23 8:11 ` Gao Xiang
2025-12-23 1:56 ` [PATCH v10 08/10] erofs: support unencoded inodes for page cache share Hongbo Li
2025-12-23 8:15 ` Gao Xiang
2025-12-23 8:34 ` Gao Xiang
2025-12-23 1:56 ` [PATCH v10 09/10] erofs: support compressed " Hongbo Li
2025-12-23 8:18 ` 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=65cf64e7-c395-4508-9bac-5a8dc08e8f3c@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
all inboxes | Powered by JetHome®