From: Andreas Hindborg <nmi@metaspace.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: Matias Bjorling <Matias.Bjorling@wdc.com>,
linux-kernel@vger.kernel.org (open list),
Damien Le Moal <dlemoal@kernel.org>, Jens Axboe <axboe@kernel.dk>,
gost.dev@samsung.com, Christoph Hellwig <hch@infradead.org>,
Andreas Hindborg <a.hindborg@samsung.com>,
Johannes Thumshirn <jth@kernel.org>,
Aravind Ramesh <Aravind.Ramesh@wdc.com>,
linux-block@vger.kernel.org (open list:BLOCK LAYER),
Hans Holmberg <Hans.Holmberg@wdc.com>,
Minwoo Im <minwoo.im.dev@gmail.com>
Subject: [PATCH v9 0/2] ublk: enable zoned storage support
Date: Fri, 14 Jul 2023 09:25:08 +0200 [thread overview]
Message-ID: <20230714072510.47770-1-nmi@metaspace.dk> (raw)
From: Andreas Hindborg <a.hindborg@samsung.com>
Hi All,
This patch set adds zoned storage support to `ublk`. The first patch does some
house cleaning in preparation for the last patch. The last patch adds support
for report_zones and the following operations:
- REQ_OP_ZONE_OPEN
- REQ_OP_ZONE_CLOSE
- REQ_OP_ZONE_FINISH
- REQ_OP_ZONE_RESET
- REQ_OP_ZONE_APPEND
A user space component based on ubdsrv is available for testing [1] with the
"loop" target.
Read/write and zone operations are tested with zenfs [2].
The zone append path is tested with fio -> zonefs -> ublk -> null_blk.
The implementation of zone append requires ublk user copy feature, and therefore
the series is based on branch for-next (6afa337a3789) of [3].
Changes for v9
- Move setup of IO descriptor for zoned operations into separate function
- Fix an issue in `ublk_report_zones()` where zone report size was set to `remaining_zones` instead of `zones_in_request`
- Do not truncate bufsize to `queue_max_segments` pages in `ublk_alloc_report_buffer()`
- Do not change signature of `ublk_dev_param_basic_apply()` (not needed)
[1] https://github.com/metaspace/ubdsrv/tree/acc072e077bceea390bae14b6ccb8087f6d0cf1a
[2] https://github.com/westerndigitalcorporation/zenfs
[3] https://git.kernel.dk/linux.git
Andreas Hindborg (2):
ublk: add helper to check if device supports user copy
ublk: enable zoned storage support
drivers/block/ublk_drv.c | 342 ++++++++++++++++++++++++++++++++--
include/uapi/linux/ublk_cmd.h | 36 +++-
2 files changed, 360 insertions(+), 18 deletions(-)
base-commit: 3261ea42710e9665c9151006049411bd23b5411f
--
2.41.0
next reply other threads:[~2023-07-14 7:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 7:25 Andreas Hindborg [this message]
2023-07-14 7:25 ` [PATCH v9 1/2] ublk: add helper to check if device supports user copy Andreas Hindborg
2023-07-14 10:00 ` Johannes Thumshirn
2023-07-14 7:25 ` [PATCH v9 2/2] ublk: enable zoned storage support Andreas Hindborg
2023-07-14 10:04 ` Johannes Thumshirn
2023-07-19 9:26 ` Ming Lei
2023-07-19 12:41 ` Ming Lei
2023-08-02 10:19 ` Andreas Hindborg (Samsung)
2023-07-19 12:01 ` Niklas Cassel
2023-08-01 12:11 ` Andreas Hindborg (Samsung)
2023-08-01 12:58 ` Ming Lei
2023-08-02 9:09 ` Andreas Hindborg (Samsung)
2023-08-03 0:06 ` Ming Lei
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=20230714072510.47770-1-nmi@metaspace.dk \
--to=nmi@metaspace.dk \
--cc=Aravind.Ramesh@wdc.com \
--cc=Hans.Holmberg@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=a.hindborg@samsung.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hch@infradead.org \
--cc=jth@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=minwoo.im.dev@gmail.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
all inboxes | Powered by JetHome®