From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"hch@infradead.org" <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>,
"linux-fsdevel @ vger . kernel . org"
<linux-fsdevel@vger.kernel.org>, Daniel Wagner <dwagner@suse.de>
Subject: Re: [PATCH v7 00/11] Introduce Zone Append for writing to zoned block devices
Date: Fri, 17 Apr 2020 21:00:55 -0400 [thread overview]
Message-ID: <20200418010055.GO5187@mit.edu> (raw)
In-Reply-To: <SN4PR0401MB3598F054B867C929827E23F49BD90@SN4PR0401MB3598.namprd04.prod.outlook.com>
On Fri, Apr 17, 2020 at 05:48:20PM +0000, Johannes Thumshirn wrote:
> For "userspace's responsibility", I'd re-phrase this as "a consumer's
> responsibility", as we don't have an interface which aims at user-space
> yet. The only consumer this series implements is zonefs, although we did
> have an AIO implementation for early testing and io_uring shouldn't be
> too hard to implement.
Ah, I had assumed that userspace interface exposed would be opening
the block device with the O_APPEND flag. (Which raises interesting
questions if the block device is also opened without O_APPEND and some
other thread was writing to the same zone, in which case the order in
which requests are processed would control whether the I/O would
fail.)
- Ted
next prev parent reply other threads:[~2020-04-18 1:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 12:15 [PATCH v7 00/11] Introduce Zone Append for writing to zoned block devices Johannes Thumshirn
2020-04-17 12:15 ` [PATCH v7 01/11] scsi: free sgtables in case command setup fails Johannes Thumshirn
2020-04-18 16:02 ` Bart Van Assche
2020-04-20 7:10 ` Johannes Thumshirn
2020-04-20 10:46 ` Johannes Thumshirn
2020-04-22 6:44 ` hch
2020-04-17 12:15 ` [PATCH v7 02/11] block: provide fallbacks for blk_queue_zone_is_seq and blk_queue_zone_no Johannes Thumshirn
2020-04-18 16:03 ` Bart Van Assche
2020-04-17 12:15 ` [PATCH v7 03/11] block: rename __bio_add_pc_page to bio_add_hw_page Johannes Thumshirn
2020-04-17 12:15 ` [PATCH v7 04/11] block: Introduce REQ_OP_ZONE_APPEND Johannes Thumshirn
2020-04-18 16:46 ` Bart Van Assche
2020-04-20 0:30 ` Damien Le Moal
2020-04-20 0:49 ` Bart Van Assche
2020-04-20 1:08 ` Damien Le Moal
2020-04-22 6:46 ` hch
2020-04-17 12:15 ` [PATCH v7 05/11] block: introduce blk_req_zone_write_trylock Johannes Thumshirn
2020-04-18 16:52 ` Bart Van Assche
2020-04-17 12:15 ` [PATCH v7 06/11] block: Modify revalidate zones Johannes Thumshirn
2020-04-22 6:47 ` Christoph Hellwig
2020-04-17 12:15 ` [PATCH v7 07/11] scsi: sd_zbc: factor out sanity checks for zoned commands Johannes Thumshirn
2020-04-18 16:56 ` Bart Van Assche
2020-04-17 12:15 ` [PATCH v7 08/11] scsi: sd_zbc: emulate ZONE_APPEND commands Johannes Thumshirn
2020-04-22 6:49 ` Christoph Hellwig
2020-04-17 12:15 ` [PATCH v7 09/11] null_blk: Support REQ_OP_ZONE_APPEND Johannes Thumshirn
2020-04-17 12:15 ` [PATCH v7 10/11] block: export bio_release_pages and bio_iov_iter_get_pages Johannes Thumshirn
2020-04-17 12:15 ` [PATCH v7 11/11] zonefs: use REQ_OP_ZONE_APPEND for sync DIO Johannes Thumshirn
2020-04-18 21:45 ` Bart Van Assche
2020-04-20 0:36 ` Damien Le Moal
2020-04-17 16:03 ` [PATCH v7 00/11] Introduce Zone Append for writing to zoned block devices Theodore Y. Ts'o
2020-04-17 17:48 ` Johannes Thumshirn
2020-04-18 1:00 ` Theodore Y. Ts'o [this message]
2020-04-18 8:57 ` Johannes Thumshirn
2020-04-19 22:51 ` Damien Le Moal
2020-04-18 15:56 ` Bart Van Assche
2020-04-20 0:21 ` Damien Le Moal
2020-04-20 1:06 ` Douglas Gilbert
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=20200418010055.GO5187@mit.edu \
--to=tytso@mit.edu \
--cc=Damien.LeMoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@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 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).