virtio net requirements for 1.4
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v5 Latest7 patches 9 repliesIn review
- v47 patches 22 repliesSuperseded
- v27 patches 9 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 | 7 patches | 0 replies | Superseded |
Changes in v5 from the cover letter
- Refined receive flow filter requirements to be ready for spec draft
- updated timestamp requirement to feedback from Willem
- Fixed counters rquirements on comments from David
Patches in v5 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | net-features: Add requirements document for release 1.4net-workstream/ | +41 | 1 reply | |
| 2/7 | net-features: Add low latency transmit queue requirementsnet-workstream/ | +88 | 0 replies | |
| 3/7 | net-features: Add low latency receive queue requirementsnet-workstream/ | +44 | 4 replies | |
| 4/7 | net-features: Add notification coalescing requirementsnet-workstream/ | +11 | 0 replies | |
| 5/7 | net-features: Add n-tuple receive flow filters requirementsnet-workstream/ | +163 | 3 replies | |
| 6/7 | net-features: Add packet timestamp requirementsnet-workstream/ | +24 | 0 replies | |
| 7/7 | net-features: Add header data split requirementsnet-workstream/ | +13 | 1 reply |
Reviews trailers per patch
5 of 7 patches have a Reviewed-by or Acked-by.
| Patch | David Edmondson |
|---|---|
| 1/7 | A-b |
| 2/7 | A-b |
| 3/7 | |
| 4/7 | A-b |
| 5/7 | |
| 6/7 | A-b |
| 7/7 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [virtio-comment] [PATCH requirements v5 0/7] virtio net requirements for 1.4
Hi All,
This document captures the virtio net device requirements for the upcoming release 1.4 that some of us are currently working on.
This is live document to be updated in coming time and work towards it for its design which can result in a draft specification.
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 list of requirements that can be practical to achieve in 1.4 timeframe incrementally and also have the ability to implement them.
Please review mainly patch 5 at the priority.
Receive flow filters is the first item apart from counters to complete in this iteration to start drafting the design spec. Rest of the requirements are largly untouched other than Stefan's comment.
TODO:
1. Some more refinement needed for rx low latency and header data split requirements.
changelog:v4->v5:
- Refined receive flow filter requirements to be ready for spec draft
- updated timestamp requirement to feedback from Willem
- Fixed counters rquirements on comments from Davidv3->v4:
- receive flow filters requirements undergo major updates to take to spec draft level.
- Addressed comments from Xuan, Heng, David, Satananda.
- Refined wordings in rest of the requirementsv2->v3:
- addressed comments from Stefan for tx low latency and notification
- redrafted the requirements to use rearm term and avoid queue enable confusion for notification
- addressed all comments and refined receive flow filters requirements to take to design levelv1->v2:
- major update of receive flow filter requirements updated based on last two design discussions in community and offline research
- examples added
- link to use case and design goal added
- control and operation side requirements split
- more verbosev0->v1:
- addressed comments from Heng Li
- addressed few (not all) comments from Michael
- per patch changelog
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 filters requirements
net-features: Add packet timestamp requirements
net-features: Add header data split requirements
net-workstream/features-1.4.md | 383 +++++++++++++++++++++++++++++++++ 1 file changed, 383 insertions(+) create mode 100644 net-workstream/features-1.4.md
Signature · 18 lines
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/