From: Jens Axboe <axboe@kernel.dk>
To: "Matias Bjørling" <mb@lightnvm.io>, loberman@redhat.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Bart.VanAssche@wdc.com, Damien.LeMoal@wdc.com
Subject: Re: [PATCH 0/2] null_blk: zone support
Date: Mon, 9 Jul 2018 10:34:26 -0600 [thread overview]
Message-ID: <4421a151-85d9-52e4-2233-03ed7f17528a@kernel.dk> (raw)
In-Reply-To: <296d2d14-0bf6-e0a2-84dc-7d6e819625c1@lightnvm.io>
On 7/9/18 1:54 AM, Matias Bjørling wrote:
> For fio, you can use the zone support here:
>
> https://github.com/bvanassche/fio
>
> It is in the process of being upstreamed.
In the spirit of making some progress on this, I just don't like how
it's done. For example, it should not be necessary to adjust what
comes out of the block generator, instead the block generator should
be told to do what we need on zbc. This is a key concept. The workload
should be defined as such that it works for zoned devices.
The trim as zone resets seems odd. What happens if you end up with a
zoned flash device in the future?
The support code looks fine.
--
Jens Axboe
next prev parent reply other threads:[~2018-07-09 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 17:38 [PATCH 0/2] null_blk: zone support Matias Bjørling
2018-07-06 17:38 ` [PATCH 1/2] null_blk: move shared definitions to header file Matias Bjørling
2018-07-06 17:38 ` [PATCH 2/2] null_blk: add zone support Matias Bjørling
2018-07-06 17:45 ` [PATCH 0/2] null_blk: " Laurence Oberman
2018-07-09 7:54 ` Matias Bjørling
2018-07-09 16:34 ` Jens Axboe [this message]
2018-07-10 0:05 ` Bart Van Assche
2018-07-10 14:46 ` Jens Axboe
2018-07-10 16:47 ` Bart Van Assche
2018-07-10 18:45 ` Jens Axboe
2018-07-10 18:49 ` Bart Van Assche
2018-07-10 18:51 ` Jens Axboe
2018-08-09 20:51 ` Zoned block device support for fio (was: [PATCH 0/2] null_blk: zone support) Bart Van Assche
2018-08-09 21:03 ` Zoned block device support for fio Jens Axboe
2018-08-15 18:07 ` Bart Van Assche
2018-07-07 2:54 ` [PATCH 0/2] null_blk: zone support Jens Axboe
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=4421a151-85d9-52e4-2233-03ed7f17528a@kernel.dk \
--to=axboe@kernel.dk \
--cc=Bart.VanAssche@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=mb@lightnvm.io \
/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;
as well as URLs for NNTP newsgroup(s).