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 4/7] net-features: Add notification coalescing requirements
Date: Mon, 3 Jul 2023 02:44:07 +0300	[thread overview]
Message-ID: <20230702234410.47546-5-parav@nvidia.com> (raw)
In-Reply-To: <20230702234410.47546-1-parav@nvidia.com>

Add virtio net device notification coalescing improvements requirements.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
changelog:
v0->v1:
- updated the description
---
 net-workstream/features-1.4.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/net-workstream/features-1.4.md b/net-workstream/features-1.4.md
index 3e8b5a4..a34556c 100644
--- a/net-workstream/features-1.4.md
+++ b/net-workstream/features-1.4.md
@@ -8,6 +8,7 @@ together is desired while updating the virtio net interface.
 # 2. Summary
 1. Device counters visible to the driver
 2. Low latency tx and rx virtqueues for PCI transport
+3. Virtqueue notification coalescing re-arming support
 
 # 3. Requirements
 ## 3.1 Device counters
@@ -157,3 +158,14 @@ struct vnet_rx_completion {
    which can be recycled by the driver when the packets from the completed
    page is fully consumed.
 8. The device should be able to consume multiple pages for a receive GSO stream.
+
+## 3.3 Virtqueue notification coalescing re-enable support
+0. Design goal:
+   a. Avoid constant notification from the device even in conditions when
+      the driver may not have acted on the previous pending notification.
+1. When Tx and Rx virtqueue notification coalescing is enabled, and when such
+   notification is reported by the device, device should be able to disable
+   further notifications until the driver finish reacting to the already
+   generated notification. 
+2. When the driver enables the notification coalescing reporting, the device
+   to notify again if notification coalescing conditions are met.
-- 
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/


  parent 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 [virtio-comment] [PATCH REQUIREMENTS v2 0/7] virtio net new features requirements Parav Pandit
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 ` Parav Pandit [this message]
2023-07-20 15:19   ` [virtio-comment] Re: [virtio] [PATCH REQUIREMENTS v2 4/7] net-features: Add notification coalescing requirements 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-5-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