From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>, jaegeuk@kernel.org
Cc: ke.wang@unisoc.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, Hao_hao.Wang@unisoc.com
Subject: Re: [f2fs-dev] [PATCH V2] f2fs-io: unify default block size
Date: Thu, 31 Oct 2024 15:45:49 +0800 [thread overview]
Message-ID: <0c03d45e-d62e-4bd8-b9d9-68651dd4179f@kernel.org> (raw)
In-Reply-To: <1730190466-13015-1-git-send-email-zhiguo.niu@unisoc.com>
On 2024/10/29 16:27, Zhiguo Niu wrote:
> F2FS_BLKSIZE and 4096 are both used in f2fs_io for
> IO/buffer size, but F2FS_BLKSIZE may confuse user becasue
> it may be 4KB, 16KB, so use macro F2FS_DEFAULT_BLKSIZE
> to unify F2FS_BLKSIZE and 4096 in f2fs_io, also adjust
> "-c" parameters in mkfs man, to be consistent with commit
> c35fa8cd75ac ("mkfs.f2fs: change -c option description").
>
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.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
prev parent reply other threads:[~2024-10-31 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 8:27 [f2fs-dev] [PATCH V2] f2fs-io: unify default block size Zhiguo Niu
2024-10-31 7:45 ` Chao Yu via Linux-f2fs-devel [this message]
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=0c03d45e-d62e-4bd8-b9d9-68651dd4179f@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=Hao_hao.Wang@unisoc.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zhiguo.niu@unisoc.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;
as well as URLs for NNTP newsgroup(s).