OASIS Open Mailing List Archives  ·  All Lists  ·  virtio  ·  2023-06

virtio — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

[PATCH requirements 0/7] virtio net new features requirements


On Fri, Jun 2, 2023 at 6:03?AM Parav Pandit <[email protected]> wrote: > > Hi All, > > This document captures the virtio net device requirements for the upcoming > release 1.4 that some of us are currently working on. > > I would like to capture if there are any other requirements linked to the > features captured in this document to consider in the interface design. > > The objectives are: > 1. to consider these requirements in introducing new features > listed in the document and work towards the interface design followed > by drafting the specification changes. > > 2. Define practical list of requirements that can be achieved in 1.4 > timeframe incrementally and also have the ability to implement them. > > This is not a specification document. It is a pre-work document > that helps to understand the draft specification addressing these > requirements. > > Please review. > > Parav Pandit (7): > net-features: Add requirements document for release 1.4 > net-features: Add low latency transmit queue requirements > net-features: Add low latency receive queue requirements > net-features: Add notification coalescing requirements > net-features: Add n-tuple receive flow steering requirements > net-features: Add packet timestamp requirements > net-features: Add header data split requirements > > net-workstream/features-1.4.md | 224 +++++++++++++++++++++++++++++++++ I feel that some patches go into too many details of the proposed solution which makes it more like RFC instead of a requirement. It would be easier to start with to describe why a feature is needed and why it can't work well in current spec. Thanks > 1 file changed, 224 insertions(+) > create mode 100644 net-workstream/features-1.4.md > > -- > 2.26.2 > > > This publicly archived list offers a means to provide input to the > OASIS Virtual I/O Device (VIRTIO) TC. > > In order to verify user consent to the Feedback License terms and > to minimize spam in the list archive, subscription is required > before posting. > > Subscribe: [email protected] > Unsubscribe: [email protected] > List help: [email protected] > List archive: https://lists.oasis-open.org/archives/virtio-comment/ > Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf > List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists > Committee: https://www.oasis-open.org/committees/virtio/ > Join OASIS: https://www.oasis-open.org/join/ >

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]