From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Kelvin Zhang <zhangxp1998@gmail.com>,
linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v9 08/11] f2fs: parameterize sector conversion macros
Date: Fri, 4 Sep 2026 10:16:07 +0800 [thread overview]
Message-ID: <1004a0bc-2321-45dd-aed5-e2d35133cd8f@kernel.org> (raw)
In-Reply-To: <534c0147c80d739938e90cc9f1c349fc9ae3f6fd.1788479509.git.zhangxp1998@gmail.com>
On 9/4/26 07:56, Kelvin Zhang wrote:
> Sector-to-block and block-to-sector conversion helpers previously
> assumed a fixed sector count per block derived from 4KB pages.
>
> Parameterize F2FS_LOG_SECTORS_PER_BLOCK, SECTOR_FROM_BLOCK, and
> SECTOR_TO_BLOCK with struct f2fs_sb_info *sbi, using
> sbi->log_sectors_per_block.
>
> Update all call sites across metadata I/O, data mapping, discard
> operations, and zoned block device reporting.
>
> Signed-off-by: Kelvin Zhang <zhangxp1998@gmail.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
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:[~2026-09-04 2:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 23:54 [f2fs-dev] [PATCH v9 00/11] f2fs: prepare metadata layouts for runtime block sizes Kelvin Zhang
2026-09-03 23:54 ` [f2fs-dev] [PATCH v9 01/11] f2fs: initialize sb_info early in f2fs_fill_super Kelvin Zhang
2026-09-04 1:48 ` Chao Yu via Linux-f2fs-devel
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 02/11] f2fs: describe SIT block layout dynamically Kelvin Zhang
2026-09-04 1:54 ` Chao Yu via Linux-f2fs-devel
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 03/11] f2fs: describe NAT " Kelvin Zhang
2026-09-04 1:55 ` Chao Yu via Linux-f2fs-devel
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 04/11] f2fs: describe orphan " Kelvin Zhang
2026-09-04 1:56 ` Chao Yu via Linux-f2fs-devel
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 05/11] f2fs: describe dentry " Kelvin Zhang
2026-09-04 1:58 ` Chao Yu via Linux-f2fs-devel
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 06/11] f2fs: describe {i, d, id}node " Kelvin Zhang
2026-09-04 2:08 ` Chao Yu via Linux-f2fs-devel
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 07/11] f2fs: describe xattr " Kelvin Zhang
2026-09-04 2:15 ` Chao Yu via Linux-f2fs-devel
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 08/11] f2fs: parameterize sector conversion macros Kelvin Zhang
2026-09-04 2:16 ` Chao Yu via Linux-f2fs-devel [this message]
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 09/11] f2fs: parameterize byte and block " Kelvin Zhang
2026-09-04 2:17 ` Chao Yu via Linux-f2fs-devel
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 10/11] f2fs: describe node tree geometry dynamically Kelvin Zhang
2026-09-04 2:18 ` Chao Yu via Linux-f2fs-devel
2026-09-03 23:56 ` [f2fs-dev] [PATCH v9 11/11] f2fs: parameterize block size and mask macros Kelvin Zhang
2026-09-04 2:20 ` Chao Yu via Linux-f2fs-devel
2026-09-08 20:00 ` [f2fs-dev] [PATCH v9 00/11] f2fs: prepare metadata layouts for runtime block sizes 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=1004a0bc-2321-45dd-aed5-e2d35133cd8f@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhangxp1998@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.