|
Should the TC accept changes listed in the description to resolve issue 143,
for inclusion in specification version(s) "virtio-v1.3-cs01", and future versions of the specification?
Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
If you don't have an opinion, please vote Abstain.
I move that:
The TC agrees to resolve the following specification issue:
Issue #143: virtio-blk: add zoned block device specification
--------------------------------------
Introduce support for Zoned Block Devices (ZBDs) to virtio.
The virtio protocol for block devices (virtio-blk) is not aware of ZBDs but it allows the guest to successfully scan a host-managed zoned drive provided by as a virtio-blk device. As the result, the host-managed drive appears at the virtio-blk driver as a regular drive that will operate erroneously under the most common write workloads. Host-aware ZBDs are currently usable, but their performance is not optimal because the driver can only recoginze them as non-zoned block devices.
To properly support ZBDs, the virtio-blk protocol needs to be extended to add the capabilities to convey the zone characteristics of ZBDs to the driver and to provide the support for ZBD-specific commands.
The patch linked below extends the virtio-blk section of virtio specification with the minimum set of requirements that are necessary to support ZBDs.
[https://lists.oasis-open.org/archives/virtio-comment/202211/msg00002.html](https://lists.oasis-open.org/archives/virtio-comment/202211/msg00002.html)
The patch series to implement this spec extension in Linux kernel virtio-blk driver code has been posted to linux-block mailing list -
[https://lore.kernel.org/linux-block/20221110053952.3378990-1-dmitry.fomichev@wdc.com/](https://lore.kernel.org/linux-block/20221110053952.3378990-1-dmitry.fomichev@wdc.com/)
The patch series to add ZBD support to QEMU virtio codebase by Sam Li that follow this spec are in review at the QEMU mailing list -
[https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05195.html](https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05195.html)
[https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05205.html](https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05205.html)
[https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05896.html](https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg05896.html)
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202211/msg00002.html](https://lists.oasis-open.org/archives/virtio-comment/202211/msg00002.html)
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-cs01", and future versions of the
specification.
--------------------------------------
Reminder: A Voting Member must be active in a TC to maintain voting rights. As
the Virtio TC has adopted a standing rule to conduct business only by
electronic ballot, without Meetings, a Voting Member who fails to cast a ballot
in two consecutive Work Product Ballots loses his or her voting rights at the
close of the second ballot missed.
--------------------------------------
|
