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 07/11] f2fs: describe xattr block layout dynamically
Date: Fri, 4 Sep 2026 10:15:37 +0800 [thread overview]
Message-ID: <e179d20c-4ba7-46dd-8835-29ba00247998@kernel.org> (raw)
In-Reply-To: <c7005ebefcad46d6a0bf3b0653fbd3692b86a360.1788479509.git.zhangxp1998@gmail.com>
On 9/4/26 07:56, Kelvin Zhang wrote:
> The usable capacity of dedicated on-disk extended attribute blocks and
> inline xattr regions scales with the filesystem block size.
>
> Parameterize VALID_XATTR_BLOCK_SIZE and MAX_INLINE_XATTR_SIZE to
> calculate usable xattr limits dynamically from sbi->blocksize rather than
> hardcoding PAGE_SIZE or DEF_ADDRS_PER_INODE.
>
> Update mount option consistency validation for inline_xattr_size to
> evaluate allowed boundaries dynamically against the runtime block size.
>
> 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:15 UTC|newest]
Thread overview: 23+ 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 [this message]
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
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
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=e179d20c-4ba7-46dd-8835-29ba00247998@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox