From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>
Subject: [PATCH v3 0/2] New zoned loop block device driver
Date: Mon, 7 Apr 2025 16:52:20 +0900 [thread overview]
Message-ID: <20250407075222.170336-1-dlemoal@kernel.org> (raw)
This patch series implements the new "zloop" zoned block device driver
which allows creating zoned block devices using one regular file per
zone as backing storage. This driver is an alternative to the RUST
rublk driver which provide a similar functionality using ublk
(See https://github.com/ublk-org/rublk.git). However, zloop is far
simpler to use (a single shell command to setup and teardown a device)
and does not have any user space dependencies. These characteristics
make zloop a better solution for integration in test environments (such
as xfstests) using small VMs.
zloop and rublk performance is generally comparable. zloop is a bit
faster for large sequential write operations than rublk, while rublk is
faster for small zone-random write IOs.
The first patch implements the "zloop" zoned block device driver under
drivers/block. The second patch adds documentation for this driver
(overview and usage examples).
About half of the code of the first patch is from Christoph Hellwig.
Damien Le Moal (2):
block: new zoned loop block device driver
Documentation: Document the new zoned loop block device driver
Changes from v2:
- Rebased on 6.15-rc1
- Some corrections of the documentation
Changes from v1:
- Corrected Kconfig description in patch 1 (outdated example was shown)
- Added missing request sector update on completion of zone append
request (I had not pushed that...)
- Added reference to the documentation in the kconfig entry in patch 2
Damien Le Moal (2):
block: new zoned loop block device driver
Documentation: Document the new zoned loop block device driver
Documentation/admin-guide/blockdev/index.rst | 1 +
.../admin-guide/blockdev/zoned_loop.rst | 169 ++
MAINTAINERS | 8 +
drivers/block/Kconfig | 19 +
drivers/block/Makefile | 1 +
drivers/block/zloop.c | 1385 +++++++++++++++++
6 files changed, 1583 insertions(+)
create mode 100644 Documentation/admin-guide/blockdev/zoned_loop.rst
create mode 100644 drivers/block/zloop.c
--
2.49.0
next reply other threads:[~2025-04-07 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 7:52 Damien Le Moal [this message]
2025-04-07 7:52 ` [PATCH v3 1/2] block: new zoned loop block device driver Damien Le Moal
2025-04-07 7:52 ` [PATCH v3 2/2] Documentation: Document the " Damien Le Moal
2025-04-08 6:37 ` Christoph Hellwig
2025-04-08 7:51 ` [PATCH v3 0/2] New " Johannes Thumshirn
2025-05-01 18:29 ` Damien Le Moal
2025-05-01 23:04 ` 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=20250407075222.170336-1-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/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.