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 1/7] net-features: Add requirements document for release 1.4
Date: Mon, 24 Jul 2023 06:34:15 +0300	[thread overview]
Message-ID: <20230724033421.249893-2-parav@nvidia.com> (raw)
In-Reply-To: <20230724033421.249893-1-parav@nvidia.com>

Add requirements document template for the virtio net features.

Add virtio net device counters visible to driver.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
changelog:
v0->v1:
- removed tx dropped counter
- updated requirements to mention about virtqueue interface for counters
  query
---
 net-workstream/features-1.4.md | 35 ++++++++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 net-workstream/features-1.4.md

diff --git a/net-workstream/features-1.4.md b/net-workstream/features-1.4.md
new file mode 100644
index 0000000..4c3797b
--- /dev/null
+++ b/net-workstream/features-1.4.md
@@ -0,0 +1,35 @@
+# 1. Introduction
+
+This document describes the overall requirements for virtio net device
+improvements for upcoming release 1.4. Some of these requirements are
+interrelated and influence the interface design, hence reviewing them
+together is desired while updating the virtio net interface.
+
+# 2. Summary
+1. Device counters visible to the driver
+
+# 3. Requirements
+## 3.1 Device counters
+1. The driver should be able to query the device and/or per vq counters for
+   debugging purpose using a virtqueue directly from driver to device for
+   example using a control vq.
+2. The driver should be able to query which counters are supported using a
+   virtqueue command, for example using an existing control vq.
+3. If this device is migrated between two hosts, the driver should be able
+   get the counter values in the destination host from where it was left
+   off in the source host.
+4. If a virtio device is group member device, a group owner should be able
+   to query all the counter attributes using the administration command which
+   a virtio member device will expose via a virtqueue to the driver.
+
+### 3.1.1 Per receive queue counters
+1. le64 rx_oversize_pkt_errors: Packet dropped due to receive packet being
+    oversize than the buffer size
+2. le64 rx_no_buffer_pkt_errors: Packet dropped due to unavailability of the
+    buffer in the receive queue
+3. le64 rx_gro_pkts: Packets treated as receive GSO sequence by the device
+4. le64 rx_pkts: Total packets received by the device
+
+### 3.1.2 Per transmit queue counters
+1. le64 tx_gso_pkts: Packets send as transmit GSO sequence
+2. le64 tx_pkts: Total packets send by the device
-- 
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-24  3:35 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  3:34 [virtio-comment] [PATCH requirements 0/7] virtio net new features requirements Parav Pandit
2023-07-24  3:34 ` Parav Pandit [this message]
2023-08-08  8:16   ` [virtio-comment] [PATCH requirements 1/7] net-features: Add requirements document for release 1.4 David Edmondson
2023-08-14  5:17     ` Parav Pandit
2023-08-14 11:53       ` David Edmondson
2023-08-14 11:56   ` David Edmondson
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 2/7] net-features: Add low latency transmit queue requirements Parav Pandit
2023-08-08  8:24   ` David Edmondson
2023-08-10 19:05   ` [virtio-comment] RE: [EXT] [virtio] " Satananda Burla
2023-08-15  5:51     ` Parav Pandit
2023-08-14 11:55   ` [virtio-comment] " David Edmondson
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 3/7] net-features: Add low latency receive " Parav Pandit
2023-08-08  8:32   ` David Edmondson
2023-08-14 11:54   ` David Edmondson
2023-08-15  4:45     ` 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
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 5/7] net-features: Add n-tuple receive flow filters requirements Parav Pandit
2023-08-01  8:33   ` [virtio-comment] " Parav Pandit
2023-08-02  6:44     ` Parav Pandit
2023-08-02 15:32       ` Heng Qi
2023-08-03 10:01         ` Parav Pandit
2023-08-03 13:11           ` [virtio-comment] Re: [virtio] " Heng Qi
2023-08-02  7:17   ` [virtio-comment] RE: [EXT] [virtio] " Satananda Burla
2023-08-02  8:14     ` Parav Pandit
2023-08-02 18:32       ` Satananda Burla
2023-08-04  7:32         ` Parav Pandit
2023-08-02 15:25   ` [virtio-comment] " Heng Qi
2023-08-03  9:59     ` [virtio-comment] " Parav Pandit
2023-08-03 13:07       ` [virtio-comment] " Heng Qi
2023-08-04  6:20         ` [virtio-comment] " Parav Pandit
2023-08-04  7:17           ` [virtio-comment] " Heng Qi
2023-08-04  7:30             ` [virtio-comment] " Parav Pandit
2023-08-04  7:51               ` [virtio-comment] Re: [virtio] " Heng Qi
2023-08-07  7:22                 ` Heng Qi
2023-08-08  7:13                   ` Parav Pandit
2023-08-08  8:18                     ` [virtio-comment] Re: [virtio] " Heng Qi
2023-08-08  8:21       ` [virtio-comment] " Heng Qi
2023-08-14  5:15         ` [virtio-comment] " Parav Pandit
2023-08-14  6:18           ` [virtio-comment] " Heng Qi
2023-08-14  6:35             ` [virtio-comment] " Parav Pandit
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 6/7] net-features: Add packet timestamp requirements Parav Pandit
2023-08-09  8:35   ` [virtio-comment] Re: [virtio] " Xuan Zhuo
2023-08-10  6:56     ` Jason Wang
2023-08-15  6:13       ` Parav Pandit
     [not found]       ` <CAF=yD-+LMY3yE3qtd4vHc8CGOz6UAf4njM2QiZcajrQgL=KZRQ@mail.gmail.com>
2023-08-14  2:54         ` Jason Wang
2023-08-15  6:26         ` Parav Pandit
     [not found]           ` <CAF=yD-LXtrQeW0GnTR0BeDuExN5aBLC4dGEfdWbjtxmhNY2G6g@mail.gmail.com>
2023-08-16  4:10             ` Parav Pandit
2023-08-14 13:06     ` [virtio-comment] " Parav Pandit
2023-08-15  2:47       ` [virtio-comment] " Xuan Zhuo
2023-08-15  4:01         ` [virtio-comment] " Parav Pandit
2023-08-15  6:01           ` [virtio-comment] " Xuan Zhuo
2023-08-15  6:09             ` [virtio-comment] " Parav Pandit
2023-08-15  9:44               ` [virtio-comment] " Xuan Zhuo
2023-08-14 11:59   ` [virtio-comment] " David Edmondson
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 7/7] net-features: Add header data split requirements Parav Pandit
2023-08-10 19:19   ` [virtio-comment] RE: [EXT] [virtio] " Satananda Burla
2023-08-14 12:00   ` [virtio-comment] " David Edmondson
     [not found]     ` <CA+FuTSeguCKk4zxZ0=Ebr1phZhF9kssHeGPn2eZj6SRNv2ewsA@mail.gmail.com>
2023-08-14 13:09       ` [virtio-comment] Re: [virtio] " David Edmondson
2023-08-14 13:28         ` [virtio-comment] " Parav Pandit
2023-08-14 13:56           ` [virtio-comment] " David Edmondson
2023-08-15  4:41             ` [virtio-comment] " Parav Pandit
  -- strict thread matches above, loose matches on Subject: below --
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 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

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=20230724033421.249893-2-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