From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.oasis-open.org>, <hengqi@linux.alibaba.com>,
<david.edmondson@oracle.com>, <xuanzhuo@linux.alibaba.com>,
<sburla@marvell.com>
Cc: <shahafs@nvidia.com>, <virtio@lists.oasis-open.org>,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] [PATCH requirements v5 0/7] virtio net requirements for 1.4
Date: Fri, 18 Aug 2023 07:35:50 +0300 [thread overview]
Message-ID: <20230818043557.496964-1-parav@nvidia.com> (raw)
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 David
v3->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 requirements
v2->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 level
v1->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 verbose
v0->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
--
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: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
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/
next reply other threads:[~2023-08-18 4:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 4:35 Parav Pandit [this message]
2023-08-18 4:35 ` [virtio-comment] [PATCH requirements v5 1/7] net-features: Add requirements document for release 1.4 Parav Pandit
2023-08-21 10:44 ` David Edmondson
2023-08-18 4:35 ` [virtio-comment] [PATCH requirements v5 2/7] net-features: Add low latency transmit queue requirements Parav Pandit
2023-08-18 4:35 ` [virtio-comment] [PATCH requirements v5 3/7] net-features: Add low latency receive " Parav Pandit
2023-08-21 10:47 ` [virtio-comment] " David Edmondson
2023-08-22 6:12 ` [virtio-comment] " Parav Pandit
2023-09-11 13:47 ` [virtio-comment] Re: [virtio] " Stefan Hajnoczi
2023-09-11 16:03 ` [virtio-comment] " Parav Pandit
2023-08-18 4:35 ` [virtio-comment] [PATCH requirements v5 4/7] net-features: Add notification coalescing requirements Parav Pandit
2023-08-18 4:35 ` [virtio-comment] [PATCH requirements v5 5/7] net-features: Add n-tuple receive flow filters requirements Parav Pandit
2023-08-21 5:06 ` [virtio-comment] " Heng Qi
2023-08-21 5:14 ` [virtio-comment] " Parav Pandit
2023-08-22 7:41 ` Parav Pandit
2023-08-18 4:35 ` [virtio-comment] [PATCH requirements v5 6/7] net-features: Add packet timestamp requirements Parav Pandit
2023-08-18 4:35 ` [virtio-comment] [PATCH requirements v5 7/7] net-features: Add header data split requirements Parav Pandit
2023-08-21 10:45 ` [virtio-comment] " David Edmondson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230818043557.496964-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=david.edmondson@oracle.com \
--cc=hengqi@linux.alibaba.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).