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:
VIRTIO-144: VIRTIO_BLK_F_CONFIG_WCE removed from block devices spec
--------------------------------------
VIRTIO_BLK_F_CONFIG_WCE is important in order to achieve good performance (up to 2x, though more realistically +30-40%) in latency-bound workloads. However, it was removed by mistake together with VIRTIO_BLK_F_FLUSH.
The lack of this feature means that virtio 1.0 cs02 does not achieve parity with 0.9.
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
Clarify definition of writeback and writethrough caching, clarify the influence of the
VIRTIO_BLK_F_FLUSH feature on caching, strengthen the requirement for persisting writes to MUST after a VIRTIO_BLK_T_FLUSH request (and in other cases too involving the new features), introduce VIRTIO_BLK_F_FLUSH and VIRTIO_BLK_F_CONFIG_WCE for non-transitional devices.
https://lists.oasis-open.org/archives/virtio/201508/msg00024.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio 1.0 cs04", 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.
-------------------------------------- |
