From: David Edmondson <david.edmondson@oracle.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "hengqi@linux.alibaba.com" <hengqi@linux.alibaba.com>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
"sburla@marvell.com" <sburla@marvell.com>,
Shahaf Shuler <shahafs@nvidia.com>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>
Subject: Re: [virtio-comment] [PATCH requirements v4 1/7] net-features: Add requirements document for release 1.4
Date: Tue, 15 Aug 2023 10:14:25 +0100 [thread overview]
Message-ID: <m2leec64zu.fsf@oracle.com> (raw)
In-Reply-To: <PH0PR12MB54817DE0F0C993C548982279DC14A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tuesday, 2023-08-15 at 09:11:18 UTC, Parav Pandit wrote:
>> From: David Edmondson <david.edmondson@oracle.com>
>> Sent: Tuesday, August 15, 2023 2:26 PM
>
>
>> > +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.
>>
>> The language seems confusing here. How about:
>>
>> If a virtio device is a group member device, it must be possible to query all of
>> the group member counter attributes via the group owner device.
>>
>> > +4. If a virtio device is a group member device, a group owner should be able
>> > + to query all of the member device counter attributes and counters via the
>> > + group owner device.
>>
>> Similarly:
>>
>> If a virtio device is a group member device, it must be possible to query all of
>> the group member counters via the group owner device.
>>
> I messed up this point 4 while addressing your comments from v3.
>
> How about,
>
> If a virtio device is a group member device, it must be possible to query supported counters bitmap through the group owner device.
> The group owner driver should be able to query such bitmap using administration command.
>
> Notice that group owner only cares for the supported bitmap, no need to query the counters through this interface.
Why do we think this is the case? It would be useful for a group owner
to be able to see the statistics as they are being reported to the
member consumer.
> With this we can reuse single structure across AQ and CVQ to learn about supported bitmap in v14 patch from Xuan.
Makes sense.
--
I'm not living in the real world, no more, no more.
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-08-15 10:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 7:45 [virtio-comment] [PATCH requirements v4 0/7] virtio net requirements for 1.4 Parav Pandit
2023-08-15 7:45 ` [virtio-comment] [PATCH requirements v4 1/7] net-features: Add requirements document for release 1.4 Parav Pandit
2023-08-15 8:56 ` David Edmondson
2023-08-15 9:11 ` Parav Pandit
2023-08-15 9:14 ` David Edmondson [this message]
2023-08-15 12:20 ` Parav Pandit
2023-08-15 7:45 ` [virtio-comment] [PATCH requirements v4 2/7] net-features: Add low latency transmit queue requirements Parav Pandit
2023-08-15 8:45 ` [virtio-comment] " David Edmondson
2023-08-15 8:50 ` [virtio-comment] " Parav Pandit
2023-08-15 7:45 ` [virtio-comment] [PATCH requirements v4 3/7] net-features: Add low latency receive " Parav Pandit
2023-08-15 8:50 ` [virtio-comment] " David Edmondson
2023-08-15 7:45 ` [virtio-comment] [PATCH requirements v4 4/7] net-features: Add notification coalescing requirements Parav Pandit
2023-08-16 8:30 ` [virtio-comment] " Heng Qi
2023-08-16 10:46 ` [virtio-comment] " Parav Pandit
2023-08-16 12:36 ` [virtio-comment] " Heng Qi
2023-08-17 4:57 ` [virtio-comment] " Parav Pandit
2023-08-17 5:13 ` [virtio-comment] " Heng Qi
2023-08-17 5:20 ` [virtio-comment] " Parav Pandit
2023-08-15 7:45 ` [virtio-comment] [PATCH requirements v4 5/7] net-features: Add n-tuple receive flow filters requirements Parav Pandit
2023-08-16 6:27 ` [virtio-comment] " Parav Pandit
2023-08-16 7:38 ` [virtio-comment] " Heng Qi
2023-08-16 10:31 ` [virtio-comment] " Parav Pandit
2023-08-16 11:10 ` [virtio-comment] " Heng Qi
2023-08-16 11:18 ` [virtio-comment] " Parav Pandit
2023-08-16 11:42 ` [virtio-comment] " Heng Qi
2023-08-17 4:52 ` [virtio-comment] " Parav Pandit
2023-08-17 5:14 ` [virtio-comment] " Heng Qi
2023-08-15 7:45 ` [virtio-comment] [PATCH requirements v4 6/7] net-features: Add packet timestamp requirements Parav Pandit
2023-08-15 7:46 ` [virtio-comment] [PATCH requirements v4 7/7] net-features: Add header data split requirements Parav Pandit
2023-08-15 8:52 ` [virtio-comment] " 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=m2leec64zu.fsf@oracle.com \
--to=david.edmondson@oracle.com \
--cc=hengqi@linux.alibaba.com \
--cc=parav@nvidia.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.