Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>, jasowang@redhat.com
Cc: virtio-dev@lists.oasis-open.org
Subject: [virtio-dev] Re: [PATCH v8] virtio-net: support device stats
Date: Tue, 11 Jan 2022 15:52:20 +0100	[thread overview]
Message-ID: <87zgo2wcij.fsf@redhat.com> (raw)
In-Reply-To: <20220111040125.11735-1-xuanzhuo@linux.alibaba.com>

On Tue, Jan 11 2022, Xuan Zhuo <xuanzhuo@linux.alibaba.com> wrote:

> This patch allows the driver to obtain some statistics from the device.
>
> In the back-end implementation, we can count a lot of such information,
> which can be used for debugging and judging the running status of the
> back-end. We hope to directly display it to the user through ethtool.
>
> Signed-off-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> Reviewed-by: Jason Wang <jasowang@redhat.com>
> ---
>
> v8:
> 1. Modified based on comments by Cornelia Huck
>
> v7:
> 1. add rx_reset, tx_reset
> 2. add device normative and dirver normative
> 3. add comments for *_packets, *_bytres
>
> v6:
> 1. correct the names and descriptions of some stats items
>
> v5:
> 1. add VIRTIO_NET_CTRL_STATS_GET_CTRL_VQ
> 2. more item for virtio_net_ctrl_reply_stats_queue_pair
>
> v4:
> 1. remove dev_stats_num, {rx|tx}_stats_num
> 2. Use two commands to get the stats of queue pair and dev respectively
>
> v3 changes:
> 1. add dev_version
> 2. use queue_pair_index replace rx_num, tx_num
> 3. Explain the processing when the device and driver support different numbers
> of stats
>
>  conformance.tex |   2 +
>  content.tex     | 133 +++++++++++++++++++++++++++++++++++++++++++++++-
>  2 files changed, 134 insertions(+), 1 deletion(-)

LGTM.

Unless someone else spots a problem, I think this is ready to vote on,
so please open a github issue and link it here.


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2022-01-11 14:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  4:01 [PATCH v8] virtio-net: support device stats Xuan Zhuo
2022-01-11 14:52 ` Cornelia Huck [this message]
2022-01-11 14:58   ` [virtio-dev] " Xuan Zhuo
2022-01-15 18:17 ` [virtio-dev] " Michael S. Tsirkin
2022-01-17  2:14   ` Xuan Zhuo
2022-01-17  7:06     ` Jason Wang
2022-01-17  7:16       ` Xuan Zhuo
2022-01-18  3:26         ` Jason Wang
2022-01-18  3:34           ` Xuan Zhuo
2022-01-18  7:16             ` Michael S. Tsirkin
2022-01-18  7:37               ` Xuan Zhuo
2022-01-17  8:12     ` Michael S. Tsirkin
2022-01-17  8:21       ` Xuan Zhuo
2022-01-17 14:13         ` Michael S. Tsirkin
2022-01-18  1:49           ` Xuan Zhuo
2022-01-18  8:39             ` Cornelia Huck
2022-01-18  8:58               ` Xuan Zhuo
2022-01-18  9:14                 ` Cornelia Huck

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=87zgo2wcij.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=virtio-dev@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