From: Laurence Oberman <loberman@redhat.com>
To: "Matias Bjørling" <mb@lightnvm.io>, axboe@fb.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: Fri, 06 Jul 2018 13:45:18 -0400 [thread overview]
Message-ID: <1530899118.31977.1.camel@redhat.com> (raw)
In-Reply-To: <20180706173839.28355-1-mb@lightnvm.io>
On Fri, 2018-07-06 at 19:38 +0200, Matias Bjørling wrote:
> This series adds support for exposing a zone block device using the
> null_blk device driver.
>
> The first patch moves core null_blk data structures to a shared
> header
> file. The second implements the actual zone support. The patchset
> adds
> two new options. One to enable the zone interface, and another to
> define the size of the zones to expose.
>
> Thanks,
> Matias
>
> Matias Bjørling (2):
> null_blk: move shared definitions to header file
> null_blk: add zone support
>
> Documentation/block/null_blk.txt | 7 ++
> drivers/block/Makefile | 5 +-
> drivers/block/null_blk.c | 124 ++++++++++++-----------------
> ---
> drivers/block/null_blk.h | 108 ++++++++++++++++++++++++++++
> drivers/block/null_blk_zoned.c | 149
> +++++++++++++++++++++++++++++++++++++++
> 5 files changed, 315 insertions(+), 78 deletions(-)
> create mode 100644 drivers/block/null_blk.h
> create mode 100644 drivers/block/null_blk_zoned.c
>
Thank you for this will be very useful.
I will test it to add value.
I dont know the code well enough to review it
Regards
Laurence
next prev parent reply other threads:[~2018-07-06 17:45 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 ` Laurence Oberman [this message]
2018-07-09 7:54 ` [PATCH 0/2] null_blk: " Matias Bjørling
2018-07-09 16:34 ` Jens Axboe
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=1530899118.31977.1.camel@redhat.com \
--to=loberman@redhat.com \
--cc=axboe@fb.com \
--cc=bart.vanassche@wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).