virtio — archive

[PATCH] virtio-net subcommittee proposal

From: Stefan Hajnoczi <[email protected]>
To: [email protected]
Date: Mon, 03 Apr 2023 14:59:00 -0000

On Fri, Mar 31, 2023 at 03:23:26AM +0300, Parav Pandit wrote: > Modern applications demand low latency and high-performance > networking devices at scale. Modernizing virtio networking devices > involves developing many complex features. While the current methodology > for developing the specification has worked well, there is an > opportunity for better collaboration to support the complex scope of modernization. > > Many hardware vendors and cloud providers have expressed interest in such virtio enhancements. > Hence, we propose to have a virtio net subcommittee. > > Subcommittee mission: Produce backward compatible, low latency, scalable virtio net device spec which works well on hardware NIC and enables efficient use of CPU and memory. > > Top objectives of the subcommittee (statement of purpose): > 1. Chartered to develop the improved virtio-net device > (features, scale, performance) which adapts to ubiquitous PCIe + PCIe virtualization > 2. Equal footing - not tied to an existing vendor s HW implementation. > The result is a backward-compatible but functionally upgraded virtio-net 2.0. > 3. Operates under virtio TC and integrate the work with master virtio specification > 4. Discuss and resolve technical issues & brainstorm on ideas and their tradeoff for near + long term > 5. Borrows best practices for workgroup progress such as NVMe, and PCI-SIG. > > Subcommittee functions: > 0. Consults virtio tc, feed and use master virtio specification for > the standard functionality across devices when applicable > 2. Continue to use OASIS open forums for spec development and reviews > 3. Have virtual technical meet weekly or bi-weekly > 4. Prioritize features design & reviews to have predictable outcomes > 5. Converge promptly and use voting as necessary > 6. A helping arm of virtio TC for virtio net device changes > 7. Listens to feedback from other industry forums and standards for next gen updates > 8. Governed by simple 4 phase review > a. usecase/problem agreement, > b. functionality/design reviews, > c. spec change reviews by subcommittee > d. submit to virtio tc for final review and vote using existing ballot > 9. Follows OASIS guidance [1] > > Spec wide bug fixes, cleanup etc continues as is. > > Everyone is welcome to join virtio net subcommittee who wish to > contribute to above mission and purpose. > > [1] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#subcommittees > > Signed-off-by: David Edmondson <[email protected]> > Signed-off-by: Dust Li <[email protected]> > Signed-off-by: Parav Pandit <[email protected]> > Signed-off-by: Satananda Burla<[email protected]> > Signed-off-by: Shahaf Shuler <[email protected]> > Signed-off-by: Xuan Zhuo <[email protected]> Why not just do this in the VIRTIO TC? The workflow and infrastructure for developing the VIRTIO spec already exists. A weekly or bi-weekly virtio-net call can be scheduled. Are you hitting scalability bottlenecks or limitations with the current VIRTIO TC? Stefan Attachment: signature.asc Description: PGP signature