Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Dmitry Fomichev <dmitry.fomichev@wdc.com>
Cc: virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Hannes Reinecke <hare@suse.de>, Cornelia Huck <cohuck@redhat.com>,
	Matias Bjorling <matias.bjorling@wdc.com>,
	Niklas Cassel <niklas.cassel@wdc.com>,
	Hans Holmberg <Hans.Holmberg@wdc.com>,
	Klaus Jensen <its@irrelevant.dk>,
	Sam Li <faithilikerun@gmail.com>
Subject: Re: [virtio-comment] [PATCH v7] virtio-blk: add zoned block device specification
Date: Mon, 31 Oct 2022 16:36:41 -0400	[thread overview]
Message-ID: <Y2Ax2XpOGRQW4dE3@fedora> (raw)
In-Reply-To: <20221031030632.992680-1-dmitry.fomichev@wdc.com>

[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]

On Sun, Oct 30, 2022 at 11:06:32PM -0400, Dmitry Fomichev wrote:

A minor issue about normative vs non-normative sections:

> +Devices that offer the VIRTIO_BLK_F_ZONED feature while reporting the
> +VIRTIO_BLK_Z_NONE zoned model are drive-managed zoned block devices. In this
> +case, the driver should treat the device as a regular non-zoned block device.

The VIRTIO spec tries to use should/may/must/etc in the drivernormative
and devicenormative sections. The non-normative sections describe the
interface without making normative statements.

Use of "should" suggests that maybe this should be in a normative
section? If you decide not to move it to a normative section then you
could simply reword it:

  "the driver treats the device as a regular ..."

> +
> +Host-managed zoned block devices have their LBA range divided into Sequential
> +Write Required (SWR) zones that require some additional handling from the host
> +for correct operation. All write requests to SWR zones must be sequential and

There is a "must" here. Same question as above.

Aside from that:

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2022-10-31 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  3:06 [PATCH v7] virtio-blk: add zoned block device specification Dmitry Fomichev
2022-10-31 20:36 ` Stefan Hajnoczi [this message]

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=Y2Ax2XpOGRQW4dE3@fedora \
    --to=stefanha@redhat.com \
    --cc=Hans.Holmberg@wdc.com \
    --cc=cohuck@redhat.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dmitry.fomichev@wdc.com \
    --cc=faithilikerun@gmail.com \
    --cc=hare@suse.de \
    --cc=its@irrelevant.dk \
    --cc=matias.bjorling@wdc.com \
    --cc=niklas.cassel@wdc.com \
    --cc=stefanha@gmail.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.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