From: Jens Axboe <axboe@kernel.dk>
To: Niklas Cassel <niklas.cassel@wdc.com>
Cc: damien.lemoal@wdc.com, johannes.thumshirn@wdc.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] null_blk: add support for max open/active zone limit for zoned devices
Date: Tue, 29 Sep 2020 08:13:02 -0600 [thread overview]
Message-ID: <ea94a097-c5c1-1996-3398-a08d64503941@kernel.dk> (raw)
In-Reply-To: <20200828105400.80893-1-niklas.cassel@wdc.com>
On 8/28/20 4:54 AM, Niklas Cassel wrote:
> Add support for user space to set a max open zone and a max active zone
> limit via configfs. By default, the default values are 0 == no limit.
>
> Call the block layer API functions used for exposing the configured
> limits to sysfs.
>
> Add accounting in null_blk_zoned so that these new limits are respected.
> Performing an operation that would exceed these limits results in a
> standard I/O error.
>
> A max open zone limit exists in the ZBC standard.
> While null_blk_zoned is used to test the Zoned Block Device model in
> Linux, when it comes to differences between ZBC and ZNS, null_blk_zoned
> mostly follows ZBC.
>
> Therefore, implement the manage open zone resources function from ZBC,
> but additionally add support for max active zones.
> This enables user space not only to test against a device with an open
> zone limit, but also to test against a device with an active zone limit.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-09-29 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 10:54 [PATCH v3] null_blk: add support for max open/active zone limit for zoned devices Niklas Cassel
2020-09-03 8:56 ` Johannes Thumshirn
2020-09-07 8:18 ` Niklas Cassel
2020-09-17 7:56 ` Niklas Cassel
2020-09-23 7:46 ` Johannes Thumshirn
2020-09-29 9:25 ` Matias Bjørling
2020-09-29 14:13 ` Jens Axboe [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=ea94a097-c5c1-1996-3398-a08d64503941@kernel.dk \
--to=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niklas.cassel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox