From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
linux-block <linux-block@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Keith Busch <kbusch@kernel.org>,
"linux-scsi @ vger . kernel . org" <linux-scsi@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 00/11] Introduce Zone Append for writing to zoned block devices
Date: Tue, 10 Mar 2020 09:42:29 -0700 [thread overview]
Message-ID: <20200310164229.GA15878@infradead.org> (raw)
In-Reply-To: <20200310094653.33257-1-johannes.thumshirn@wdc.com>
On Tue, Mar 10, 2020 at 06:46:42PM +0900, Johannes Thumshirn wrote:
> For null_blk the emulation is way simpler, as null_blk's zoned block
> device emulation support already caches the write pointer position, so we
> only need to report the position back to the upper layers. Additional
> caching is not needed here.
>
> Testing has been conducted by translating RWF_APPEND DIOs into
> REQ_OP_ZONE_APPEND commands in the block device's direct I/O function and
> injecting errors by bypassing the block layer interface and directly
> writing to the disc via the SCSI generic interface.
We really need a user of this to be useful upstream. Didn't you plan
to look into converting zonefs/iomap to use it? Without that it is
at best a RFC. Even better would be converting zonefs and the f2fs
zoned code so that can get rid of the old per-zone serialization in
the I/O scheduler entirely.
next prev parent reply other threads:[~2020-03-10 16:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 9:46 [PATCH 00/11] Introduce Zone Append for writing to zoned block devices Johannes Thumshirn
2020-03-10 9:46 ` [PATCH 01/11] block: provide fallbacks for blk_queue_zone_is_seq and blk_queue_zone_no Johannes Thumshirn
2020-03-10 9:46 ` [PATCH 02/11] block: Introduce REQ_OP_ZONE_APPEND Johannes Thumshirn
2020-03-10 9:46 ` [PATCH 03/11] block: introduce bio_add_append_page Johannes Thumshirn
2020-03-10 16:43 ` Christoph Hellwig
2020-03-11 18:11 ` Johannes Thumshirn
2020-03-10 9:46 ` [PATCH 04/11] null_blk: Support REQ_OP_ZONE_APPEND Johannes Thumshirn
2020-03-10 16:43 ` Christoph Hellwig
2020-03-10 9:46 ` [PATCH 05/11] block: introduce BLK_STS_ZONE_RESOURCE Johannes Thumshirn
2020-03-10 16:43 ` Christoph Hellwig
2020-03-10 9:46 ` [PATCH 06/11] block: introduce blk_req_zone_write_trylock Johannes Thumshirn
2020-03-10 9:46 ` [PATCH 07/11] block: factor out requeue handling from dispatch code Johannes Thumshirn
2020-03-10 16:44 ` Christoph Hellwig
2020-03-10 9:46 ` [PATCH 08/11] block: delay un-dispatchable request Johannes Thumshirn
2020-03-10 16:45 ` Christoph Hellwig
2020-03-10 9:46 ` [PATCH 09/11] block: Introduce zone write pointer offset caching Johannes Thumshirn
2020-03-10 16:46 ` Christoph Hellwig
2020-03-11 0:34 ` Damien Le Moal
2020-03-11 6:24 ` Christoph Hellwig
2020-03-11 6:40 ` Damien Le Moal
2020-03-10 9:46 ` [PATCH 10/11] scsi: sd_zbc: factor out sanity checks for zoned commands Johannes Thumshirn
2020-03-10 9:46 ` [PATCH 11/11] scsi: sd_zbc: emulate ZONE_APPEND commands Johannes Thumshirn
2020-03-10 17:43 ` kbuild test robot
2020-03-10 19:38 ` kbuild test robot
2020-03-10 22:43 ` kbuild test robot
2020-03-10 23:04 ` kbuild test robot
2020-03-11 0:57 ` kbuild test robot
2020-03-10 16:42 ` Christoph Hellwig [this message]
2020-03-11 0:37 ` [PATCH 00/11] Introduce Zone Append for writing to zoned block devices Damien Le Moal
2020-03-11 6:24 ` Christoph Hellwig
2020-03-11 6:40 ` Damien Le Moal
2020-03-11 7:22 ` Johannes Thumshirn
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=20200310164229.GA15878@infradead.org \
--to=hch@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=johannes.thumshirn@wdc.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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.