From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: David Edmondson <david.edmondson@oracle.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>,
"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-comment] Re: [PATCH v16 03/11] content: Rename confusing queue_notify_data and vqn names
Date: Thu, 4 May 2023 14:49:46 -0400 [thread overview]
Message-ID: <20230504144914-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB548100E1C4AD64EA35E22772DC6D9@PH0PR12MB5481.namprd12.prod.outlook.com>
On Thu, May 04, 2023 at 06:33:38PM +0000, Parav Pandit wrote:
>
> > From: David Edmondson <david.edmondson@oracle.com>
> > Sent: Thursday, May 4, 2023 10:28 AM
>
> > > \begin{description}
> > > -\item [vqn] VQ number to be notified.
> > > +\item [vq_index_config_data] Either virtqueue index or device supplied
> > > + queue notification config data corresponding to a virtqueue.
> >
> > vq_index_config_data doesn't exist.
> >
> > Given that this is an anonymous union, perhaps:
> >
> > \item [vq_index or vq_notif_config_data] Either ...
>
> > > \drivernormative{\paragraph}{Available Buffer Notifications}{Virtio
> > > Transport Options / Virtio Over PCI Bus / PCI-specific Initialization And Device
> > Operation / Available Buffer Notifications} -If VIRTIO_F_NOTIF_CONFIG_DATA
> > has been negotiated:
> > > +
> > > +If VIRTIO_F_NOTIFICATION_DATA is not negotiated, the driver
> > > +notification MUST be a 16-bit notification.
> > > +
> > > +If VIRTIO_F_NOTIFICATION_DATA is negotiated, the driver notification
> > > +MUST be a 32-bit notification.
> >
> > The above two should be inside itemize?
>
> Both suggestions look good to me.
> Given rest of the patches are reviewed and it is already v16, I think I can cover them right after this in editorial changes after merging this.
> This way the majority of the work of this series and subsequent patches doesn't need to wait another week.
Did voting start already? If not you can post a new version
just before voting if you already know what you want to do.
--
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: David Edmondson <david.edmondson@oracle.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>,
"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v16 03/11] content: Rename confusing queue_notify_data and vqn names
Date: Thu, 4 May 2023 14:49:46 -0400 [thread overview]
Message-ID: <20230504144914-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB548100E1C4AD64EA35E22772DC6D9@PH0PR12MB5481.namprd12.prod.outlook.com>
On Thu, May 04, 2023 at 06:33:38PM +0000, Parav Pandit wrote:
>
> > From: David Edmondson <david.edmondson@oracle.com>
> > Sent: Thursday, May 4, 2023 10:28 AM
>
> > > \begin{description}
> > > -\item [vqn] VQ number to be notified.
> > > +\item [vq_index_config_data] Either virtqueue index or device supplied
> > > + queue notification config data corresponding to a virtqueue.
> >
> > vq_index_config_data doesn't exist.
> >
> > Given that this is an anonymous union, perhaps:
> >
> > \item [vq_index or vq_notif_config_data] Either ...
>
> > > \drivernormative{\paragraph}{Available Buffer Notifications}{Virtio
> > > Transport Options / Virtio Over PCI Bus / PCI-specific Initialization And Device
> > Operation / Available Buffer Notifications} -If VIRTIO_F_NOTIF_CONFIG_DATA
> > has been negotiated:
> > > +
> > > +If VIRTIO_F_NOTIFICATION_DATA is not negotiated, the driver
> > > +notification MUST be a 16-bit notification.
> > > +
> > > +If VIRTIO_F_NOTIFICATION_DATA is negotiated, the driver notification
> > > +MUST be a 32-bit notification.
> >
> > The above two should be inside itemize?
>
> Both suggestions look good to me.
> Given rest of the patches are reviewed and it is already v16, I think I can cover them right after this in editorial changes after merging this.
> This way the majority of the work of this series and subsequent patches doesn't need to wait another week.
Did voting start already? If not you can post a new version
just before voting if you already know what you want to do.
--
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-05-04 18:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 2:29 [virtio-comment] [PATCH v16 00/11] Rename queue number to queue index Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 01/11] content: Add vq index text Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 14:20 ` [virtio-comment] " David Edmondson
2023-05-04 14:20 ` [virtio-dev] " David Edmondson
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 02/11] content.tex Replace virtqueue number with index Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 14:20 ` [virtio-comment] " David Edmondson
2023-05-04 14:20 ` [virtio-dev] " David Edmondson
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 03/11] content: Rename confusing queue_notify_data and vqn names Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 14:28 ` [virtio-comment] " David Edmondson
2023-05-04 14:28 ` [virtio-dev] " David Edmondson
2023-05-04 18:33 ` [virtio-comment] " Parav Pandit
2023-05-04 18:33 ` [virtio-dev] " Parav Pandit
2023-05-04 18:49 ` Michael S. Tsirkin [this message]
2023-05-04 18:49 ` [virtio-dev] " Michael S. Tsirkin
2023-05-04 19:00 ` [virtio-comment] " Parav Pandit
2023-05-04 19:00 ` [virtio-dev] " Parav Pandit
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 04/11] transport-pci: Avoid first vq index reference Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 14:28 ` [virtio-comment] " David Edmondson
2023-05-04 14:28 ` [virtio-dev] " David Edmondson
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 05/11] transport-mmio: Rename QueueNum register Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 06/11] transport-mmio: Avoid referring to zero based index Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 14:29 ` [virtio-comment] " David Edmondson
2023-05-04 14:29 ` [virtio-dev] " David Edmondson
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 07/11] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 08/11] transport-ccw: Refer to the vq by its index Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 09/11] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 10/11] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 14:30 ` [virtio-comment] " David Edmondson
2023-05-04 14:30 ` [virtio-dev] " David Edmondson
2023-05-04 2:29 ` [virtio-comment] [PATCH v16 11/11] virtio-net: Update vqn to vq_index for cvq cmds Parav Pandit
2023-05-04 2:29 ` [virtio-dev] " Parav Pandit
2023-05-04 14:31 ` [virtio-comment] " David Edmondson
2023-05-04 14:31 ` [virtio-dev] " 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=20230504144914-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=david.edmondson@oracle.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.