From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-comment] Re: [virtio-dev] [PATCH v13 03/11] content: Rename confusing queue_notify_data and vqn names
Date: Tue, 18 Apr 2023 02:04:10 -0400 [thread overview]
Message-ID: <20230418020150-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB548148EDDB407D4B1A3E316ADC9C9@PH0PR12MB5481.namprd12.prod.outlook.com>
On Mon, Apr 17, 2023 at 08:53:32PM +0000, Parav Pandit wrote:
> > > @@ -1053,9 +1059,9 @@ \subsubsection{Available Buffer
> > > Notifications}\label{sec:Virtio Transport Option If
> > VIRTIO_F_NOTIF_CONFIG_DATA has been negotiated:
> > > \begin{itemize}
> > > \item If VIRTIO_F_NOTIFICATION_DATA has not been negotiated, the
> > > driver MUST use the -\field{queue_notify_data} value instead of the virtqueue
> > index.
> > > +\field{queue_notify_id} value instead of the virtqueue index.
> > > \item If VIRTIO_F_NOTIFICATION_DATA has been negotiated, the driver
> > > MUST set the -\field{vqn} field to the \field{queue_notify_data} value.
> > > +\field{vq_notify_id} field to the \field{queue_notify_id} value.
> >
> > Seems you did not catch these with the s/_id/_config_data/. By doing the
> > replace one would get queue_notify_config_data, vq_notify_config_data and
> > queue_notify_config_data respectively.
> >
> > But that still does not seem right, and the right answer depends on to what do
> > we rename \field{vqn}.
> >
> vqn -> vq_notif_config_data in the notification structure.
>
> virtio_pci_common_cfg.queue_notify_data -> queue_notify_config_data.
>
> Better to rename
>
> VIRTIO_F_NOTIF_CONFIG_DATA to VIRTIO_F_NOTIFY_CONFIG_DATA.
> Adding "Y" is not going to make it that long. Field names will have some consistency.
> WDYT?
I think this NOTIF stands for "notification", not "notify".
--
MST
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/
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: Re: [virtio-dev] [PATCH v13 03/11] content: Rename confusing queue_notify_data and vqn names
Date: Tue, 18 Apr 2023 02:04:10 -0400 [thread overview]
Message-ID: <20230418020150-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB548148EDDB407D4B1A3E316ADC9C9@PH0PR12MB5481.namprd12.prod.outlook.com>
On Mon, Apr 17, 2023 at 08:53:32PM +0000, Parav Pandit wrote:
> > > @@ -1053,9 +1059,9 @@ \subsubsection{Available Buffer
> > > Notifications}\label{sec:Virtio Transport Option If
> > VIRTIO_F_NOTIF_CONFIG_DATA has been negotiated:
> > > \begin{itemize}
> > > \item If VIRTIO_F_NOTIFICATION_DATA has not been negotiated, the
> > > driver MUST use the -\field{queue_notify_data} value instead of the virtqueue
> > index.
> > > +\field{queue_notify_id} value instead of the virtqueue index.
> > > \item If VIRTIO_F_NOTIFICATION_DATA has been negotiated, the driver
> > > MUST set the -\field{vqn} field to the \field{queue_notify_data} value.
> > > +\field{vq_notify_id} field to the \field{queue_notify_id} value.
> >
> > Seems you did not catch these with the s/_id/_config_data/. By doing the
> > replace one would get queue_notify_config_data, vq_notify_config_data and
> > queue_notify_config_data respectively.
> >
> > But that still does not seem right, and the right answer depends on to what do
> > we rename \field{vqn}.
> >
> vqn -> vq_notif_config_data in the notification structure.
>
> virtio_pci_common_cfg.queue_notify_data -> queue_notify_config_data.
>
> Better to rename
>
> VIRTIO_F_NOTIF_CONFIG_DATA to VIRTIO_F_NOTIFY_CONFIG_DATA.
> Adding "Y" is not going to make it that long. Field names will have some consistency.
> WDYT?
I think this NOTIF stands for "notification", not "notify".
--
MST
---------------------------------------------------------------------
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-18 6:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 19:23 [virtio-comment] [PATCH v13 00/11] Rename queue number to queue index Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 01/11] content: Add vq index text Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-18 14:12 ` [virtio-comment] " Halil Pasic
2023-04-18 14:12 ` [virtio-dev] " Halil Pasic
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 02/11] content.tex Replace virtqueue number with index Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 03/11] content: Rename confusing queue_notify_data and vqn names Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-17 3:41 ` [virtio-comment] " Halil Pasic
2023-04-17 3:41 ` Halil Pasic
2023-04-17 20:53 ` [virtio-comment] " Parav Pandit
2023-04-17 20:53 ` Parav Pandit
2023-04-18 6:04 ` Michael S. Tsirkin [this message]
2023-04-18 6:04 ` Michael S. Tsirkin
2023-04-18 11:39 ` [virtio-comment] " Halil Pasic
2023-04-18 11:39 ` Halil Pasic
2023-04-18 11:43 ` [virtio-comment] " Michael S. Tsirkin
2023-04-18 11:43 ` Michael S. Tsirkin
2023-04-18 12:13 ` [virtio-comment] " Parav Pandit
2023-04-18 12:13 ` Parav Pandit
2023-04-18 12:06 ` [virtio-comment] " Parav Pandit
2023-04-18 12:06 ` Parav Pandit
2023-04-18 12:31 ` [virtio-comment] " Cornelia Huck
2023-04-18 12:31 ` [virtio-dev] " Cornelia Huck
2023-04-18 13:17 ` [virtio-comment] " Cornelia Huck
2023-04-18 13:17 ` Cornelia Huck
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 04/11] transport-pci: Avoid first vq index reference Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 05/11] transport-mmio: Rename QueueNum register Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 06/11] transport-mmio: Avoid referring to zero based index Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 07/11] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 08/11] transport-ccw: Refer to the vq by its index Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-18 16:54 ` [virtio-comment] " Halil Pasic
2023-04-18 16:54 ` [virtio-dev] " Halil Pasic
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 09/11] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 10/11] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-04-11 19:23 ` [virtio-dev] " Parav Pandit
2023-04-11 19:23 ` [virtio-comment] [PATCH v13 11/11] virtio-net: Update vqn to vq_index for cvq cmds Parav Pandit
2023-04-11 19:23 ` [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=20230418020150-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@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 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.