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 v5] f2fs: fix zoned block device information initialization
Date: Sun, 4 Feb 2024 11:13:49 +0800 [thread overview]
Message-ID: <30907165-9727-451e-8955-0e26cd219fdb@kernel.org> (raw)
In-Reply-To: <20240204031022.1189-1-qwjhust@gmail.com>
On 2024/2/4 11:10, 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.
>
> Signed-off-by: Wenjie Qi <qwjhust@gmail.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2024-02-04 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 3:10 [PATCH v5] f2fs: fix zoned block device information initialization Wenjie Qi
2024-02-04 3:13 ` Chao Yu [this message]
2024-02-04 3:35 ` Yongpeng Yang
2024-02-04 4:53 ` Yongpeng Yang
2024-02-04 7:29 ` 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=30907165-9727-451e-8955-0e26cd219fdb@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