From: Christoph Hellwig <hch@lst.de>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: cleanup AOP_WRITEPAGE_ACTIVATE use in f2fs v2
Date: Thu, 8 May 2025 07:14:26 +0200 [thread overview]
Message-ID: <20250508051520.4169795-1-hch@lst.de> (raw)
Hi all,
this almost entirely cleans up usage of AOP_WRITEPAGE_ACTIVATE in f2fs.
Changes since v1:
- pick up the bug fix from Chao as patch 1
- release the folio batch on early exit
- remove the dead for_reclaim handling
- keep the ability of the caller to exit early for the redity case
Diffstat:
fs/f2fs/checkpoint.c | 36 ++++++++----------------
fs/f2fs/compress.c | 3 --
fs/f2fs/data.c | 23 ++-------------
fs/f2fs/file.c | 1
fs/f2fs/node.c | 65 ++++++++++++++++++--------------------------
include/trace/events/f2fs.h | 5 ---
6 files changed, 46 insertions(+), 87 deletions(-)
next reply other threads:[~2025-05-08 5:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 5:14 Christoph Hellwig [this message]
2025-05-08 5:14 ` [PATCH 1/6] f2fs: fix to return correct error number in f2fs_sync_node_pages() Christoph Hellwig
2025-05-08 16:30 ` [f2fs-dev] " patchwork-bot+f2fs
2025-05-08 5:14 ` [PATCH 2/6] f2fs: return bool from __f2fs_write_meta_folio Christoph Hellwig
2025-05-08 5:14 ` [PATCH 3/6] f2fs: remove wbc->for_reclaim handling Christoph Hellwig
2025-05-08 9:46 ` Chao Yu
2025-05-08 5:14 ` [PATCH 4/6] f2fs: always unlock the page in f2fs_write_single_data_page Christoph Hellwig
2025-05-08 9:48 ` Chao Yu
2025-05-08 5:14 ` [PATCH 5/6] f2fs: simplify return value handling in f2fs_fsync_node_pages Christoph Hellwig
2025-05-08 9:53 ` Chao Yu
2025-05-08 5:14 ` [PATCH 6/6] f2fs: return bool from __write_node_folio Christoph Hellwig
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=20250508051520.4169795-1-hch@lst.de \
--to=hch@lst.de \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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®