From: Chao Yu <chao@kernel.org>
To: jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH v3 6/9] f2fs: convert f2fs_write_data_page() to use folio
Date: Tue, 20 Aug 2024 22:55:04 +0800 [thread overview]
Message-ID: <20240820145507.1372905-6-chao@kernel.org> (raw)
In-Reply-To: <20240820145507.1372905-1-chao@kernel.org>
Convert to use folio, so that we can get rid of 'page->index' to
prepare for removal of 'index' field in structure page [1].
[1] https://lore.kernel.org/all/Zp8fgUSIBGQ1TN0D@casper.infradead.org/
Cc: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Chao Yu <chao@kernel.org>
---
fs/f2fs/data.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index c57ddee2c7c5..e69097267b99 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -2945,22 +2945,23 @@ int f2fs_write_single_data_page(struct folio *folio, int *submitted,
static int f2fs_write_data_page(struct page *page,
struct writeback_control *wbc)
{
+ struct folio *folio = page_folio(page);
#ifdef CONFIG_F2FS_FS_COMPRESSION
- struct inode *inode = page->mapping->host;
+ struct inode *inode = folio->mapping->host;
if (unlikely(f2fs_cp_error(F2FS_I_SB(inode))))
goto out;
if (f2fs_compressed_file(inode)) {
- if (f2fs_is_compressed_cluster(inode, page->index)) {
- redirty_page_for_writepage(wbc, page);
+ if (f2fs_is_compressed_cluster(inode, folio->index)) {
+ folio_redirty_for_writepage(wbc, folio);
return AOP_WRITEPAGE_ACTIVATE;
}
}
out:
#endif
- return f2fs_write_single_data_page(page_folio(page), NULL, NULL, NULL,
+ return f2fs_write_single_data_page(folio, NULL, NULL, NULL,
wbc, FS_DATA_IO, 0, true);
}
--
2.40.1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-08-20 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 14:54 [f2fs-dev] [PATCH v3 1/9] f2fs: convert f2fs_submit_page_read() to use folio Chao Yu
2024-08-20 14:55 ` [f2fs-dev] [PATCH v3 2/9] f2fs: convert f2fs_write_begin() " Chao Yu
2024-08-20 14:55 ` [f2fs-dev] [PATCH v3 3/9] f2fs: convert f2fs_write_end() " Chao Yu
2024-08-20 14:55 ` [f2fs-dev] [PATCH v3 4/9] f2fs: convert f2fs_set_compressed_page() " Chao Yu
2024-08-20 14:55 ` [f2fs-dev] [PATCH v3 5/9] f2fs: convert f2fs_do_write_data_page() " Chao Yu
2024-08-20 14:55 ` Chao Yu [this message]
2024-08-20 14:55 ` [f2fs-dev] [PATCH v3 7/9] f2fs: convert __write_node_page() " Chao Yu
2024-08-20 14:55 ` [f2fs-dev] [PATCH v3 8/9] f2fs: convert read_node_page() " Chao Yu
2024-08-20 14:55 ` [f2fs-dev] [PATCH v3 9/9] f2fs: get rid of page->index Chao Yu
2024-08-21 11:01 ` [f2fs-dev] [PATCH v3 1/9] f2fs: convert f2fs_submit_page_read() to use folio Li Zetao via Linux-f2fs-devel
2024-08-30 20:51 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
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=20240820145507.1372905-6-chao@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).