From: Daeho Jeong <daeho43@gmail.com>
To: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: Daeho Jeong <daehojeong@google.com>
Subject: [PATCH v2] f2fs-tools: allocate logs after conventional area for HM zoned devices
Date: Wed, 31 Jan 2024 10:33:06 -0800 [thread overview]
Message-ID: <20240131183306.536372-1-daeho43@gmail.com> (raw)
From: Daeho Jeong <daehojeong@google.com>
Make to allocate logs after conventional area for HM zoned devices to
spare them for file pinning support.
Signed-off-by: Daeho Jeong <daehojeong@google.com>
---
v2: make current segment numbers relative to main start block. check
zoned block availability before the allocation.
---
mkfs/f2fs_format.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/mkfs/f2fs_format.c b/mkfs/f2fs_format.c
index f2840c8..57ea9ea 100644
--- a/mkfs/f2fs_format.c
+++ b/mkfs/f2fs_format.c
@@ -558,6 +558,16 @@ static int f2fs_prepare_super_block(void)
c.cur_seg[CURSEG_WARM_DATA] = next_zone(CURSEG_COLD_DATA);
} else if (c.zoned_mode) {
c.cur_seg[CURSEG_HOT_NODE] = 0;
+ if (c.zoned_model == F2FS_ZONED_HM) {
+ uint32_t conv_zones =
+ c.devices[0].total_segments / c.segs_per_zone
+ - total_meta_zones;
+
+ if (total_zones - conv_zones >= avail_zones)
+ c.cur_seg[CURSEG_HOT_NODE] =
+ (c.devices[1].start_blkaddr -
+ get_sb(main_blkaddr)) / c.blks_per_seg;
+ }
c.cur_seg[CURSEG_WARM_NODE] = next_zone(CURSEG_HOT_NODE);
c.cur_seg[CURSEG_COLD_NODE] = next_zone(CURSEG_WARM_NODE);
c.cur_seg[CURSEG_HOT_DATA] = next_zone(CURSEG_COLD_NODE);
--
2.43.0.429.g432eaa2c6b-goog
next reply other threads:[~2024-01-31 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 18:33 Daeho Jeong [this message]
2024-02-01 10:12 ` [f2fs-dev] [PATCH v2] f2fs-tools: allocate logs after conventional area for HM zoned devices Chao Yu
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=20240131183306.536372-1-daeho43@gmail.com \
--to=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--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