From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Parav Pandit <parav@nvidia.com>
Cc: virtio-dev@lists.oasis-open.org, sgarzare@redhat.com,
pasic@linux.ibm.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com
Subject: [virtio-dev] Re: [PATCH v12 03/10] content: Rename confusing queue_notify_data and vqn names
Date: Wed, 05 Apr 2023 11:57:36 +0200 [thread overview]
Message-ID: <87jzyqr6r3.fsf@redhat.com> (raw)
In-Reply-To: <20230405012723-mutt-send-email-mst@kernel.org>
On Wed, Apr 05 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Apr 05, 2023 at 04:06:50AM +0300, Parav Pandit wrote:
>> diff --git a/content.tex b/content.tex
>> index cd93db2..d5f8026 100644
>> --- a/content.tex
>> +++ b/content.tex
>> @@ -405,8 +405,18 @@ \section{Driver Notifications} \label{sec:Basic Facilities of a Virtio Device /
>> notification to the device.
>>
>> When VIRTIO_F_NOTIFICATION_DATA has not been negotiated,
>> -this notification involves sending the
>> -virtqueue index to the device (method depending on the transport).
>> +this notification involves sending only the 16-bit virtqueue notification
>> +identifier (notification method depends on the transport).
>> +
>> +\begin{itemize}
>> +\item When VIRTIO_F_NOTIF_CONFIG_DATA is not negotiated, virtqueue
>> +notification identifier is a 16-bit vq index.
>> +
>> +\item When VIRTIO_F_NOTIF_CONFIG_DATA is negotiated, virtqueue
>> +notification identifier is a device supplied virtqueue identifier. A method
>> +to supply such virtqueue notification identifier is transport
>> +specific.
>> +\end{itemize}
>>
>> However, some devices benefit from the ability to find out the
>> amount of available data in the queue without accessing the virtqueue in memory:
>
>
> VIRTIO_F_NOTIF_CONFIG_DATA is such a narrow usecase, I don't like
> burning "vq identifier" on this. How about we just say something
> along the lines of:
>
>
> When VIRTIO_F_NOTIFICATION_DATA has not been negotiated, this
> notification involves sending either the virtqueue index or the
> virtqueue config data to the device (method depending on the
> transport).
>
> And then "the data sent is a device supplied virtqueue config data".
Agreed, referring to "virtqueue configuration data" or somesuch is
better than using up the "vq identifier" name for it.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-04-05 9:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 1:06 [virtio-dev] [PATCH v12 00/10] Rename queue number to queue index Parav Pandit
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 01/10] content: Add vq index text Parav Pandit
2023-04-05 5:26 ` [virtio-dev] " Michael S. Tsirkin
2023-04-05 13:00 ` [virtio-dev] " Parav Pandit
2023-04-05 9:18 ` [virtio-dev] " Michael S. Tsirkin
2023-04-05 13:03 ` [virtio-dev] " Parav Pandit
2023-04-07 11:30 ` Michael S. Tsirkin
2023-04-07 15:34 ` Parav Pandit
2023-04-07 15:54 ` Michael S. Tsirkin
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 02/10] content.tex Replace virtqueue number with index Parav Pandit
2023-04-05 9:46 ` [virtio-dev] " Cornelia Huck
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 03/10] content: Rename confusing queue_notify_data and vqn names Parav Pandit
2023-04-05 5:22 ` [virtio-dev] " Michael S. Tsirkin
2023-04-05 13:20 ` [virtio-dev] " Parav Pandit
2023-04-10 13:25 ` [virtio-dev] " Michael S. Tsirkin
2023-04-05 5:30 ` Michael S. Tsirkin
2023-04-05 9:57 ` Cornelia Huck [this message]
2023-04-05 13:21 ` [virtio-dev] " Parav Pandit
2023-04-05 15:27 ` Halil Pasic
2023-04-05 15:58 ` Parav Pandit
2023-04-07 11:43 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-11 8:56 ` Cornelia Huck
2023-04-11 13:35 ` [virtio-dev] " Parav Pandit
2023-04-17 3:18 ` [virtio-dev] " Halil Pasic
2023-04-17 7:04 ` Michael S. Tsirkin
2023-04-17 8:47 ` [virtio-dev] Participation (was: Re: [virtio-comment] RE: [virtio-dev] RE: [PATCH v12 03/10] content: Rename confusing queue_notify_data and vqn names) Cornelia Huck
2023-04-17 11:45 ` [virtio-dev] " Michael S. Tsirkin
2023-04-17 16:13 ` [virtio-dev] Re: [virtio-comment] RE: [virtio-dev] RE: [PATCH v12 03/10] content: Rename confusing queue_notify_data and vqn names Halil Pasic
2023-04-07 11:44 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 04/10] transport-pci: Avoid first vq index reference Parav Pandit
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 05/10] transport-mmio: Rename QueueNum register Parav Pandit
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 06/10] transport-mmio: Avoid referring to zero based index Parav Pandit
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 07/10] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 08/10] transport-ccw: Refer to the vq by its index Parav Pandit
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 09/10] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-04-05 1:06 ` [virtio-dev] [PATCH v12 10/10] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-04-05 9:17 ` [virtio-dev] " Michael S. Tsirkin
2023-04-05 13:02 ` [virtio-dev] " Parav Pandit
2023-04-07 11:32 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-05 5:32 ` [virtio-dev] Re: [PATCH v12 00/10] Rename queue number to queue index Michael S. Tsirkin
2023-04-05 13:11 ` [virtio-dev] " Parav Pandit
2023-04-05 9:20 ` [virtio-dev] " Michael S. Tsirkin
2023-04-05 13:05 ` [virtio-dev] " Parav Pandit
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=87jzyqr6r3.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=sgarzare@redhat.com \
--cc=shahafs@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