From: Yohan Joung <jyh429@gmail.com>
To: jaegeuk@kernel.org, chao@kernel.org, daeho43@gmail.com
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Yohan Joung <yohan.joung@sk.com>
Subject: [PATCH v2] mkfs.f2fs: adjust zone alignment when using convention partition with zoned one
Date: Tue, 29 Oct 2024 22:45:51 +0900 [thread overview]
Message-ID: <20241029134551.252-1-yohan.joung@sk.com> (raw)
When formatting conventional partition with zoned one, we are already
aligning the starting block address of the next device to the zone size.
Therefore, we do not align the segment0 address to the zone alignment.
This reduces the wasted zone_align_start_offset.
Test result
segment0 blkaddr 389583 -> 119251
Add one additional section to main
Signed-off-by: Yohan Joung <yohan.joung@sk.com>
---
mkfs/f2fs_format.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/mkfs/f2fs_format.c b/mkfs/f2fs_format.c
index a01b19e..52a1e18 100644
--- a/mkfs/f2fs_format.c
+++ b/mkfs/f2fs_format.c
@@ -266,6 +266,7 @@ static int f2fs_prepare_super_block(void)
uint32_t log_sectorsize, log_sectors_per_block;
uint32_t log_blocksize, log_blks_per_seg;
uint32_t segment_size_bytes, zone_size_bytes;
+ uint32_t alignment_bytes;
uint32_t sit_segments, nat_segments;
uint32_t blocks_for_sit, blocks_for_nat, blocks_for_ssa;
uint32_t total_valid_blks_available;
@@ -305,10 +306,12 @@ static int f2fs_prepare_super_block(void)
set_sb(block_count, c.total_sectors >> log_sectors_per_block);
+ alignment_bytes = c.zoned_mode && c.ndevs > 1 ? segment_size_bytes : zone_size_bytes;
+
zone_align_start_offset =
((uint64_t) c.start_sector * DEFAULT_SECTOR_SIZE +
- 2 * F2FS_BLKSIZE + zone_size_bytes - 1) /
- zone_size_bytes * zone_size_bytes -
+ 2 * F2FS_BLKSIZE + alignment_bytes - 1) /
+ alignment_bytes * alignment_bytes -
(uint64_t) c.start_sector * DEFAULT_SECTOR_SIZE;
if (c.feature & F2FS_FEATURE_RO)
@@ -327,7 +330,8 @@ static int f2fs_prepare_super_block(void)
if (c.zoned_mode && c.ndevs > 1)
zone_align_start_offset +=
- (c.devices[0].total_sectors * c.sector_size) % zone_size_bytes;
+ (c.devices[0].total_sectors * c.sector_size -
+ zone_align_start_offset) % zone_size_bytes;
set_sb(segment0_blkaddr, zone_align_start_offset / blk_size_bytes);
sb->cp_blkaddr = sb->segment0_blkaddr;
--
2.25.1
next reply other threads:[~2024-10-29 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 13:45 Yohan Joung [this message]
2024-10-29 16:53 ` Daeho Jeong
2024-11-05 1:54 ` 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=20241029134551.252-1-yohan.joung@sk.com \
--to=jyh429@gmail.com \
--cc=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yohan.joung@sk.com \
/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®