All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Omar Sandoval <osandov@fb.com>,
	Omar Sandoval <osandov@osandov.com>,
	Damien Le Moal <Damien.LeMoal@wdc.com>,
	Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH blktests 2/3] block/004: Provide max_active_zones to fio command
Date: Thu, 1 Oct 2020 10:43:13 +0000	[thread overview]
Message-ID: <SN4PR0401MB3598C361CB63B30A104561879B300@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20201001104153.rbedkdqxtogzm52s@shindev.dhcp.fujisawa.hgst.com

On 01/10/2020 12:41, Shinichiro Kawasaki wrote:
> The option --max_open_zones was introduced to fio together with zonemode=zbd,
> since the beginning of fio's zoned block device support. If the test target
> device is a zoned block device, the test case block/004 checks that fio
> supports zonemode=zbd. I think this check is valid for --max_open_zones also.
> 

OK thanks for clarifying,
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>

  reply	other threads:[~2020-10-01 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 10:15 [PATCH blktests 0/3] Support max_active_zones Shin'ichiro Kawasaki
2020-10-01 10:15 ` [PATCH blktests 1/3] common/rc: Add _test_dev_max_active_zones() helper function Shin'ichiro Kawasaki
2020-10-01 10:26   ` Johannes Thumshirn
2020-10-01 10:15 ` [PATCH blktests 2/3] block/004: Provide max_active_zones to fio command Shin'ichiro Kawasaki
2020-10-01 10:25   ` Johannes Thumshirn
2020-10-01 10:41     ` Shinichiro Kawasaki
2020-10-01 10:43       ` Johannes Thumshirn [this message]
2020-10-01 10:15 ` [PATCH blktests 3/3] zbd/003: Reset zones when the test device has max_active_zones limit Shin'ichiro Kawasaki

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=SN4PR0401MB3598C361CB63B30A104561879B300@SN4PR0401MB3598.namprd04.prod.outlook.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=Chaitanya.Kulkarni@wdc.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.com \
    --cc=osandov@osandov.com \
    --cc=shinichiro.kawasaki@wdc.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.