Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.oasis-open.org>
Cc: <shahafs@nvidia.com>, <hengqi@linux.alibaba.com>,
	<virtio@lists.oasis-open.org>, Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] [PATCH REQUIREMENTS v2 0/7] virtio net new features requirements
Date: Mon, 3 Jul 2023 02:44:03 +0300	[thread overview]
Message-ID: <20230702234410.47546-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 otherwise 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.

Please review.

TODO:
1. Some more refinement needed for rx low latency and header data split
   requirements.

---
changelog:
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 | 308 +++++++++++++++++++++++++++++++++
 1 file changed, 308 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/


             reply	other threads:[~2023-07-02 23:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02 23:44 Parav Pandit [this message]
2023-07-02 23:44 ` [virtio-comment] [PATCH REQUIREMENTS v2 1/7] net-features: Add requirements document for release 1.4 Parav Pandit
2023-07-20  2:10   ` [virtio-comment] Re: [virtio] " Xuan Zhuo
2023-07-20  2:15     ` [virtio-comment] " Parav Pandit
2023-07-02 23:44 ` [virtio-comment] [PATCH REQUIREMENTS v2 2/7] net-features: Add low latency transmit queue requirements Parav Pandit
2023-07-20 15:28   ` [virtio-comment] Re: [virtio] " Stefan Hajnoczi
2023-07-23 21:31     ` [virtio-comment] " Parav Pandit
2023-07-02 23:44 ` [virtio-comment] [PATCH REQUIREMENTS v2 3/7] net-features: Add low latency receive " Parav Pandit
2023-07-02 23:44 ` [virtio-comment] [PATCH REQUIREMENTS v2 4/7] net-features: Add notification coalescing requirements Parav Pandit
2023-07-20 15:19   ` [virtio-comment] Re: [virtio] " Stefan Hajnoczi
2023-07-23 21:39     ` [virtio-comment] " Parav Pandit
2023-07-02 23:44 ` [virtio-comment] [PATCH REQUIREMENTS v2 5/7] net-features: Add n-tuple receive flow filters requirements Parav Pandit
2023-07-02 23:44 ` [virtio-comment] [PATCH REQUIREMENTS v2 6/7] net-features: Add packet timestamp requirements Parav Pandit
2023-07-02 23:44 ` [virtio-comment] [PATCH REQUIREMENTS v2 7/7] net-features: Add header data split requirements Parav Pandit
2023-07-20  2:20 ` [virtio-comment] [PATCH REQUIREMENTS v2 0/7] virtio net new features requirements Xuan Zhuo
2023-07-20  2:28   ` Parav Pandit
2023-07-20  2:36     ` Xuan Zhuo

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=20230702234410.47546-1-parav@nvidia.com \
    --to=parav@nvidia.com \
    --cc=hengqi@linux.alibaba.com \
    --cc=shahafs@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio@lists.oasis-open.org \
    /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