From: Halil Pasic <pasic@linux.ibm.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>,
Halil Pasic <pasic@linux.ibm.com>
Subject: [virtio-dev] Re: [virtio-comment] RE: [virtio-dev] RE: [PATCH v12 03/10] content: Rename confusing queue_notify_data and vqn names
Date: Mon, 17 Apr 2023 05:18:44 +0200 [thread overview]
Message-ID: <20230417051844.70ba47cc.pasic@linux.ibm.com> (raw)
In-Reply-To: <PH0PR12MB54812C754ED9063E34E06E1BDC9A9@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, 11 Apr 2023 13:35:09 +0000
Parav Pandit <parav@nvidia.com> wrote:
> > From: Cornelia Huck <cohuck@redhat.com>
> > Sent: Tuesday, April 11, 2023 4:56 AM
>
> >
> > Yes, please leave it as F_CONFIG_DATA, as we're just putting some "data"
> > there in the end (and F_CONFIG_COOKIE might indeed be confusing for the
> > ccw case.)
>
> Since Halil didn't respond for 5+ days + Michel and you propose to continue use CONFIG_DATA and this is rare used field, I will rename
>
Sorry, this one has fallen through the cracks. For
the preceding ones: I do not have a strong opinion. I do
share Michael's and Connie's assessment regarding a possible
clash with CCW.
Let me just note that the feature ain't called, "F_CONFIG_DATA" (i.e.
with full name VIRTIO_F_CONFIG_DATA) but rather "F_NOTIF_CONFIG_DATA"
(i.e. with full name VIRTIO_F_NOTIF_CONFIG_DATA).
> vqn to union of
>
> vq_index
> vq_config_data
In that sense vq_config_data is not good in my opinion, because
it misses "notif" which is present in both "F_NOTIF_CONFIG_DATA"
and "queue_notify_data".
>
> Thanks. Will roll v13.
>
I'm about tho have a look how this panned out in v13. I propose
let us continue the discussion there.
Regards,
Halil
> 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/
>
---------------------------------------------------------------------
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-17 3:18 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
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 ` Halil Pasic [this message]
2023-04-17 7:04 ` [virtio-dev] " 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=20230417051844.70ba47cc.pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.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