From: Stefan Hajnoczi <stefanha@redhat.com>
To: Sam Li <faithilikerun@gmail.com>
Cc: qemu-devel@nongnu.org, dlemoal@kernel.org,
dmitry.fomichev@wdc.com, hare@suse.de,
Markus Armbruster <armbru@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Eric Blake <eblake@redhat.com>,
Hanna Reitz <hreitz@redhat.com>
Subject: Re: [RFC 1/4] docs/qcow2: add the zoned format feature
Date: Mon, 12 Jun 2023 00:10:16 -0400 [thread overview]
Message-ID: <20230612041016.GA2446610@fedora> (raw)
In-Reply-To: <20230605104108.125270-2-faithilikerun@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2546 bytes --]
On Mon, Jun 05, 2023 at 06:41:05PM +0800, Sam Li wrote:
> Add the specs for the zoned format feature of the qcow2 driver. Once
> the zoned_profile is set to `zbc`, then the qcow2 file can be taken
> as zoned devices and passed through by virtio-blk device to the guest.
>
> Signed-off-by: Sam Li <faithilikerun@gmail.com>
> ---
> docs/system/qemu-block-drivers.rst.inc | 31 ++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/docs/system/qemu-block-drivers.rst.inc b/docs/system/qemu-block-drivers.rst.inc
> index 105cb9679c..fdcf343652 100644
> --- a/docs/system/qemu-block-drivers.rst.inc
> +++ b/docs/system/qemu-block-drivers.rst.inc
> @@ -172,6 +172,37 @@ This section describes each format and the options that are supported for it.
> filename`` to check if the NOCOW flag is set or not (Capital 'C' is
> NOCOW flag).
>
> + .. option:: zoned_profile
> +
> + The option configures the zoned format feature on the qcow2 driver. If
> + this is set to ``zbc``, then it follows the basics of ZBC/ZAC protocol.
What about virtio-blk? NVMe ZNS? Please indicate what effect the profile
has and whether it works with all emulated storage controllers that
support zoned storage.
> +
> + .. option:: zone_size
> +
> + The size of a zone of the zoned device. The zoned device have the same
"in bytes"? Please document the units.
> + size of zones with an optional smaller last zone.
"The device is divided into zones of this size with the exception of the
last zone, which may be smaller."
> +
> + .. option:: zone_capacity
> +
> + The capacity of a zone of the zoned device.
This can be expanded:
The initial capacity value for all zones. The capacity must be less
than or equal to zone size. If the last zone is smaller, then its
capacity is capped.
> The zoned device follows the
> + ZBC protocol tends to have the same size as its zone.
> +
> + .. option:: zone_nr_conv
> +
> + The number of conventional zones of the zoned device.
> +
> + .. option:: max_open_zones
> +
> + The maximal allowed open zones.
> +
> + .. option:: max_active_zones
> +
> + The limit of the zones with implicit open, explicit open or closed state.
> +
> + .. option:: max_append_sectors
> +
> + The maximal sectors that is allowed to append to zones while writing.
Does "sectors" mean 512B blocks or logical block size?
> +
> .. program:: image-formats
> .. option:: qed
>
> --
> 2.40.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-06-13 7:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 10:41 [RFC 0/4] Add full zoned storage emulation to qcow2 driver Sam Li
2023-06-05 10:41 ` [RFC 1/4] docs/qcow2: add the zoned format feature Sam Li
2023-06-12 4:10 ` Stefan Hajnoczi [this message]
2023-06-13 8:01 ` Sam Li
2023-06-05 10:41 ` [RFC 2/4] qcow2: add configurations for zoned format extension Sam Li
2023-06-05 14:50 ` Eric Blake
2023-06-19 10:10 ` Stefan Hajnoczi
2023-06-19 10:32 ` Sam Li
2023-06-19 14:42 ` Stefan Hajnoczi
2023-06-19 14:50 ` Sam Li
2023-06-20 14:44 ` Stefan Hajnoczi
2023-06-20 15:07 ` Sam Li
2023-06-05 10:41 ` [RFC 3/4] qcow2: add zoned emulation capability Sam Li
2023-06-19 14:35 ` Stefan Hajnoczi
2023-06-05 10:41 ` [RFC 4/4] iotests: test the zoned format feature for qcow2 file Sam Li
2023-06-19 14:40 ` Stefan Hajnoczi
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=20230612041016.GA2446610@fedora \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=dlemoal@kernel.org \
--cc=dmitry.fomichev@wdc.com \
--cc=eblake@redhat.com \
--cc=faithilikerun@gmail.com \
--cc=hare@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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 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).