From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.oasis-open.org>
Cc: <shahafs@nvidia.com>, <virtio@lists.oasis-open.org>,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] [PATCH requirements 4/7] net-features: Add notification coalescing requirements
Date: Fri, 2 Jun 2023 01:03:02 +0300 [thread overview]
Message-ID: <20230601220305.587034-5-parav@nvidia.com> (raw)
In-Reply-To: <20230601220305.587034-1-parav@nvidia.com>
Add virtio net device notification coalescing improvements requirements.
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
net-workstream/features-1.4.md | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/net-workstream/features-1.4.md b/net-workstream/features-1.4.md
index 054f951..fc36f31 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
@@ -143,3 +144,10 @@ struct vnet_rx_completion {
7. The device should be able to indicate when a full page buffer is consumed,
which can be recycled by the driver when the packets from the completed
page is fully consumed.
+
+## 3.3 Virtqueue notification coalescing re-enable support
+1. Tx and Rx virtqueue notification coalescing should auto-disable on
+ notification reporting to the driver. The driver should be able to enable
+ coalescing after processing the packets per VQ. This ensures that when
+ networking stack decides to poll, no new notifications are generated when
+ per VQ notification coalescing is used.
--
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 prev parent reply other threads:[~2023-06-01 22:04 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 22:02 [virtio-comment] [PATCH requirements 0/7] virtio net new features requirements Parav Pandit
2023-06-01 22:02 ` [virtio-comment] [PATCH requirements 1/7] net-features: Add requirements document for release 1.4 Parav Pandit
2023-06-06 22:15 ` Michael S. Tsirkin
2023-06-06 22:28 ` Parav Pandit
2023-06-06 22:56 ` Michael S. Tsirkin
2023-06-06 23:08 ` Parav Pandit
2023-06-06 23:18 ` Michael S. Tsirkin
2023-06-07 9:03 ` [virtio-comment] Re: [virtio] " Xuan Zhuo
2023-06-07 20:35 ` Michael S. Tsirkin
2023-06-07 20:39 ` Parav Pandit
2023-06-07 20:50 ` Michael S. Tsirkin
2023-06-07 20:53 ` Parav Pandit
2023-06-07 9:31 ` Xuan Zhuo
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 2/7] net-features: Add low latency transmit queue requirements Parav Pandit
2023-06-06 22:25 ` Michael S. Tsirkin
2023-06-06 22:35 ` Parav Pandit
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 3/7] net-features: Add low latency receive " Parav Pandit
2023-06-06 22:33 ` Michael S. Tsirkin
2023-06-06 22:44 ` Parav Pandit
2023-06-06 23:03 ` Michael S. Tsirkin
2023-06-01 22:03 ` Parav Pandit [this message]
2023-06-06 22:36 ` [virtio-comment] [PATCH requirements 4/7] net-features: Add notification coalescing requirements Michael S. Tsirkin
2023-06-06 22:46 ` Parav Pandit
2023-06-06 23:06 ` Michael S. Tsirkin
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 5/7] net-features: Add n-tuple receive flow steering requirements Parav Pandit
2023-06-02 3:35 ` Heng Qi
2023-06-02 3:51 ` Parav Pandit
2023-06-02 4:39 ` [virtio-comment] Re: [virtio] " Heng Qi
2023-06-06 12:08 ` Heng Qi
2023-06-06 21:49 ` [virtio-comment] " Parav Pandit
2023-06-12 14:35 ` [virtio-comment] " Heng Qi
2023-06-12 17:26 ` [virtio-comment] " Parav Pandit
2023-06-13 2:28 ` Heng Qi
2023-06-13 8:57 ` [virtio-comment] " Michael S. Tsirkin
2023-06-13 9:16 ` Cornelia Huck
2023-06-13 11:33 ` [virtio-comment] " Parav Pandit
2023-06-07 2:47 ` Jason Wang
2023-06-07 3:22 ` Parav Pandit
2023-06-13 2:57 ` [virtio-comment] Re: [virtio] " Heng Qi
2023-06-13 4:16 ` [virtio-comment] " Parav Pandit
2023-06-13 5:04 ` [virtio-comment] " Heng Qi
2023-06-13 12:24 ` [virtio-comment] " Parav Pandit
2023-06-14 3:43 ` [virtio-comment] " Heng Qi
2023-06-14 3:48 ` [virtio-comment] " Parav Pandit
2023-06-14 3:53 ` Heng Qi
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 6/7] net-features: Add packet timestamp requirements Parav Pandit
2023-06-06 22:40 ` Michael S. Tsirkin
2023-06-06 22:51 ` Parav Pandit
2023-06-06 23:08 ` Michael S. Tsirkin
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 7/7] net-features: Add header data split requirements Parav Pandit
2023-06-06 22:41 ` Michael S. Tsirkin
2023-06-08 14:57 ` Parav Pandit
2023-06-02 3:06 ` [virtio-comment] Re: [virtio] [PATCH requirements 0/7] virtio net new features requirements Heng Qi
2023-06-06 22:49 ` [virtio-comment] " Michael S. Tsirkin
2023-06-06 22:56 ` Parav Pandit
2023-06-06 23:10 ` Michael S. Tsirkin
2023-06-07 2:49 ` Jason Wang
2023-06-07 3:33 ` Parav Pandit
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 3:34 Parav Pandit
2023-07-24 3:34 ` [virtio-comment] [PATCH requirements 4/7] net-features: Add notification coalescing requirements Parav Pandit
2023-08-14 11:57 ` 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=20230601220305.587034-5-parav@nvidia.com \
--to=parav@nvidia.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