From: "Michael S. Tsirkin" <mst@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: Parav Pandit <parav@nvidia.com>,
Heng Qi <hengqi@linux.alibaba.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Cornelia Huck <cohuck@redhat.com>,
Alvaro Karsz <alvaro.karsz@solid-run.com>,
David Edmondson <david.edmondson@oracle.com>,
Jason Wang <jasowang@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [virtio-dev] [PATCH v14] virtio-net: support the virtqueue coalescing moderation
Date: Tue, 11 Apr 2023 06:37:09 -0400 [thread overview]
Message-ID: <20230411063315-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230405165444.1f483339.pasic@linux.ibm.com>
On Wed, Apr 05, 2023 at 04:54:44PM +0200, Halil Pasic wrote:
> On Wed, 5 Apr 2023 05:12:12 -0400
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > > > it's not necessarily an identifier. can be e.g. just 0 for all vqs.
> > > > whatever the device needs.
> > > For driver its just an id, content doesn't matter.
> >
> > No, this value might or might not be somehow related to the vq but it
> > does not have to identify it. So it's some data, not an id. Let's try
> > to use words for what they mean in english not try to come up with our
> > own language.
>
> I agree with Michael wholeheartedly, we should try to use words for what
> they mean in English, especially in Computer Science English, and even
> try to pick the most fitting and least ambiguous option if multiple
> options are possible.
>
> In that spirit I would say that "queue_notify_data" is actually a magic
> cookie. https://en.wikipedia.org/wiki/Magic_cookie A possible name
> or abbreviation would be vqn_cookie like "a virtqueue
> notification cookie" (I'm not sure about mixing in the direction, but
> this is only about driver -> device notifications).
>
>
> And then
>
> le32 {
> vqn : 16;
> next_off : 15;
> next_wrap : 1;
> };
>
> could become something like
>
> struct vq_notif_data {
> union {
> le16 vqn_cookie;
> le16 vq_index;
> };
> le16 {
> next_off : 15;
> next_wrap : 1;
> };
> };
>
> BTW since "identifier" and "unique identifier" are not the same, in my
> opinion "identifier" is still viable, if we explain that it is called
> identifier because the idea behind that field is to be used to identify
> the queue, but that there is in fact no requirement on selectivity let
> alone uniqueness.
>
>
> Regards,
> Halil
>
Well "identifier" seems to come from "identity" meaning "same" so I
think yes, it implies a 1:1 relationship.
And more importantly, it might not identify the queue, there is
in fact no requirement on how it is used at all.
--
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-11 10:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 15:24 [virtio-dev] [PATCH v14] virtio-net: support the virtqueue coalescing moderation Heng Qi
2023-03-23 15:38 ` Heng Qi
2023-04-11 8:05 ` Cornelia Huck
2023-04-11 8:42 ` Heng Qi
2023-04-11 10:32 ` Michael S. Tsirkin
2023-04-11 10:51 ` Cornelia Huck
2023-04-04 16:29 ` Halil Pasic
2023-04-04 16:32 ` Parav Pandit
2023-04-04 17:44 ` Michael S. Tsirkin
2023-04-04 19:39 ` Parav Pandit
2023-04-04 20:14 ` Michael S. Tsirkin
2023-04-04 20:50 ` Parav Pandit
2023-04-05 9:12 ` Michael S. Tsirkin
2023-04-05 14:54 ` Halil Pasic
2023-04-11 10:37 ` Michael S. Tsirkin [this message]
2023-04-07 11:45 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-10 13:33 ` Heng Qi
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=20230411063315-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox