From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "jasowang@redhat.com" <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
David Edmondson <david.edmondson@oracle.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>
Subject: Re: RE: [virtio-comment] RE: RE: [PATCH v15] virtio-net: support device stats
Date: Tue, 29 Aug 2023 19:16:19 +0800 [thread overview]
Message-ID: <1693307779.4901662-2-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <PH0PR12MB54811CB118D7D9BC36E563BCDCE7A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, 29 Aug 2023 10:58:40 +0000, Parav Pandit <parav@nvidia.com> wrote:
>
> > From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > Sent: Tuesday, August 29, 2023 12:48 PM
> >
> > For this line:
> > "If the reply header structure and actual stats are split properly, it will be easy
> > to add the query by the owner device."
> >
> > So for the header structure, is there some specific requirements?
>
> TLV type, length, is only two fields needed and to align to 64-bit.
> struct virtio_element_type {
> u16 type;
> u16 rsvd;
> u32 length;
> };
>
> Above generic type if defined, that we can possibly use across many virtio devices.
I see.
So I wonder, should we be thinking about this now. When will we try to get
statistics via aq. If we try to do this, the request data may also have to use a
uniform format.
Thanks.
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/
prev parent reply other threads:[~2023-08-29 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 6:42 [virtio-comment] [PATCH v15] virtio-net: support device stats Xuan Zhuo
2023-08-24 11:56 ` [virtio-comment] " Parav Pandit
2023-08-29 3:29 ` [virtio-comment] " Xuan Zhuo
2023-08-29 6:51 ` [virtio-comment] " Parav Pandit
2023-08-29 7:17 ` Xuan Zhuo
2023-08-29 10:58 ` Parav Pandit
2023-08-29 11:16 ` Xuan Zhuo [this message]
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=1693307779.4901662-2-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--cc=david.edmondson@oracle.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).