From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: linux-block@vger.kernel.org, Omar Sandoval <osandov@fb.com>
Cc: Omar Sandoval <osandov@osandov.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [PATCH blktests v3 0/2] Support max_open_zones and max_active_zones
Date: Tue, 29 Dec 2020 09:44:32 +0900 [thread overview]
Message-ID: <20201229004434.927644-1-shinichiro.kawasaki@wdc.com> (raw)
Linux kernel 5.9 introduced new sysfs attributes max_active_zones and
max_open_zones for zoned block devices. Blktests already handles
max_active_zones. However, max_open_zones handling is missing. Also,
zbd/005 lacks support for the two attributes.
This patch series fills the missing attributes handling. The first patch
modifies the helper function for max_active_zones to support both
max_active_zones and max_open_zones. The second patch modifies zbd/005 to
handle the attributes.
Changes from v2:
* Added Reviewed-by tags
Changes from v1:
* Reflected comments on the list
* Added Reviewed-by tags
Shin'ichiro Kawasaki (2):
common/rc: Check both max_active_zones and max_open_zones
zbd/005: Provide max_active/open_zones limit to fio command
common/rc | 19 ++++++++++++++++---
tests/block/004 | 2 +-
tests/zbd/003 | 6 +++---
tests/zbd/005 | 13 ++++++++-----
4 files changed, 28 insertions(+), 12 deletions(-)
--
2.28.0
next reply other threads:[~2020-12-29 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 0:44 Shin'ichiro Kawasaki [this message]
2020-12-29 0:44 ` [PATCH blktests v3 1/2] common/rc: Check both max_active_zones and max_open_zones Shin'ichiro Kawasaki
2020-12-29 0:44 ` [PATCH blktests v3 2/2] zbd/005: Provide max_active/open_zones limit to fio command Shin'ichiro Kawasaki
2021-01-04 22:58 ` [PATCH blktests v3 0/2] Support max_open_zones and max_active_zones Omar Sandoval
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=20201229004434.927644-1-shinichiro.kawasaki@wdc.com \
--to=shinichiro.kawasaki@wdc.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
--cc=osandov@osandov.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.