From: Chao Yu <chao@kernel.org>
To: Wenjie Qi <qwjhust@gmail.com>,
jaegeuk@kernel.org, yangyongpeng1@oppo.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Cc: hustqwj@hust.edu.cn
Subject: Re: [PATCH v4] f2fs: fix zoned block device information initialization
Date: Sun, 4 Feb 2024 09:47:49 +0800 [thread overview]
Message-ID: <8eaf59a4-1aaa-460e-a3cc-b798ed5e0f63@kernel.org> (raw)
In-Reply-To: <20240203152436.1352-1-qwjhust@gmail.com>
On 2024/2/3 23:24, Wenjie Qi wrote:
> If the max open zones of zoned devices are less than
> the active logs of F2FS, the device may error due to
> insufficient zone resources when multiple active logs are
> being written at the same time. If this value is 0,
> there is no limit.
>
> Signed-off-by: Wenjie Qi <qwjhust@gmail.com>
> ---
> fs/f2fs/f2fs.h | 1 +
> fs/f2fs/super.c | 21 +++++++++++++++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index 543898482f8b..161107f2d3bd 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -1558,6 +1558,7 @@ struct f2fs_sb_info {
>
> #ifdef CONFIG_BLK_DEV_ZONED
> unsigned int blocks_per_blkz; /* F2FS blocks per zone */
> + unsigned int max_open_zones; /* max open zone resources of the zoned device */
> #endif
>
> /* for node-related operations */
> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> index 1b718bebfaa1..45e82d6016fc 100644
> --- a/fs/f2fs/super.c
> +++ b/fs/f2fs/super.c
> @@ -2388,6 +2388,16 @@ static int f2fs_remount(struct super_block *sb, int *flags, char *data)
> if (err)
> goto restore_opts;
>
> +#ifdef CONFIG_BLK_DEV_ZONED
> + if (sbi->max_open_zones && sbi->max_open_zones < F2FS_OPTION(sbi).active_logs) {
> + f2fs_err(sbi,
> + "zoned: max open zones %u is too small, need at least %u open zones",
> + sbi->max_open_zones, F2FS_OPTION(sbi).active_logs);
> + err = -EINVAL;
> + goto restore_opts;
> + }
> +#endif
> +
> /* flush outstanding errors before changing fs state */
> flush_work(&sbi->s_error_work);
>
> @@ -3930,11 +3940,22 @@ static int init_blkz_info(struct f2fs_sb_info *sbi, int devi)
> sector_t nr_sectors = bdev_nr_sectors(bdev);
> struct f2fs_report_zones_args rep_zone_arg;
> u64 zone_sectors;
> + unsigned int max_open_zones;
> int ret;
>
> if (!f2fs_sb_has_blkzoned(sbi))
> return 0;
>
> + max_open_zones = bdev_max_open_zones(bdev);
Wenjie,
max_open_zones can always be zero? then sbi->max_open_zones will be zero,
is this a valid case?
Thanks,
> + if (max_open_zones && (max_open_zones < sbi->max_open_zones || !sbi->max_open_zones))
> + sbi->max_open_zones = max_open_zones;
> + if (sbi->max_open_zones && sbi->max_open_zones < F2FS_OPTION(sbi).active_logs) {
> + f2fs_err(sbi,
> + "zoned: max open zones %u is too small, need at least %u open zones",
> + sbi->max_open_zones, F2FS_OPTION(sbi).active_logs);
> + return -EINVAL;
> + }
> +
> zone_sectors = bdev_zone_sectors(bdev);
> if (!is_power_of_2(zone_sectors)) {
> f2fs_err(sbi, "F2FS does not support non power of 2 zone sizes\n");
next prev parent reply other threads:[~2024-02-04 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 15:24 [PATCH v4] f2fs: fix zoned block device information initialization Wenjie Qi
2024-02-04 1:47 ` Chao Yu [this message]
2024-02-04 2:18 ` Wenjie Qi
2024-02-04 2:24 ` Chao Yu
2024-02-04 2:36 ` Wenjie Qi
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=8eaf59a4-1aaa-460e-a3cc-b798ed5e0f63@kernel.org \
--to=chao@kernel.org \
--cc=hustqwj@hust.edu.cn \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=qwjhust@gmail.com \
--cc=yangyongpeng1@oppo.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