Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.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>,
	Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] Re: [PATCH 0/3] Rename queue index to queue number
Date: Mon, 27 Feb 2023 12:33:20 -0500	[thread overview]
Message-ID: <20230227123226-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481CA831447E7E7AEA46A58DCAF9@PH0PR12MB5481.namprd12.prod.outlook.com>

On Mon, Feb 27, 2023 at 04:00:24PM +0000, Parav Pandit wrote:
> 
> > From: Cornelia Huck <cohuck@redhat.com>
> > Sent: Monday, February 27, 2023 3:46 AM
> > 
> > On Thu, Feb 23 2023, Parav Pandit <parav@nvidia.com> wrote:
> > 
> > > 1. Currently, virtqueue is identified between driver and device
> > > interchangeably using either number of index terminology.
> > >
> > > 2. Between PCI and MMIO transport the queue size (depth) is defined as
> > > queue_size and QueueNum respectively.
> > >
> > > To avoid confusion and to have consistency, unify them to use as Number.
> > >
> > > Solution:
> > > Use virtqueue number description, and rename MMIO register as QueueSize.
> > >
> > > Patch summary:
> > > patch-1 renames index to number for pci transport
> > > patch-2 renames mmio register from Num to Size
> > > patch-3 renames index to number for mmio transport
> > >
> > > Please review.
> > > This series fixes the issue [1].
> > >
> > > This series is on top of [2].
> > >
> > > [1] https://github.com/oasis-tcs/virtio-spec/issues/163
> > > [2]
> > > https://lists.oasis-open.org/archives/virtio-dev/202302/msg00527.html
> > >
> > > ---
> > > Cornelia:
> > > I was not sure about ccw for vq_config_block and vq_info_block
> > > structures index field refers to the queue number or not.
> > > Can you please clarify?
> > >
> > > If it vqn, I will send v1 by replacing index to vqn to be consistent
> > > with other part of the spec which also uses vqn.
> > 
> > The vq_*_block structures use "index" for the vq index/number and "num"
> > for the number of buffers (queue size).
> > 
> Shall I change it too given the below response?
> Or ccw sync is not very interesting at this point?

I'm for changing this. I am guessing Cornelia didn't being it up
just to move some electrons around either...

> > I'm wondering what terminology we should standardize on. For the size of the
> > queue, we have queue_size, QueueNum, and num. Calling it some variation of
> > "queue size" and mentioning that it refers to the number of buffers makes
> > sense.
> > 
> > For the vq index/number, I'm not that sure that "virtqueue number" is better
> > that "virtqueue index" -- actually, I'd prefer the latter. We'd need some
> > renaming either way.
> 
> In other thread, we discussed with Michael to use vq number to align to the following ongoing work.
> 1. existing spec 
> 2. future patches that he wrote for AQ (v10)
> 3. VQ level interrupt moderation patches (v9)
> #2 and #3 uses vq number terminology.


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  parent reply	other threads:[~2023-02-27 17:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23  5:46 [PATCH 0/3] Rename queue index to queue number Parav Pandit
2023-02-23  5:46 ` [PATCH 1/3] transport-pci: Refer to the vq by its number Parav Pandit
2023-02-24 10:05   ` [virtio-dev] " Jiri Pirko
2023-02-23  5:46 ` [PATCH 2/3] transport-mmio: Rename QueueNum register Parav Pandit
2023-02-24 10:06   ` [virtio-dev] " Jiri Pirko
2023-02-27 17:36   ` Michael S. Tsirkin
2023-02-27 17:36     ` [virtio-dev] " Michael S. Tsirkin
2023-02-23  5:46 ` [PATCH 3/3] transport-mmio: Refer to the vq by its number Parav Pandit
2023-02-24 10:06   ` [virtio-dev] " Jiri Pirko
2023-02-27  8:45 ` [virtio-comment] Re: [PATCH 0/3] Rename queue index to queue number Cornelia Huck
2023-02-27  8:45   ` [virtio-dev] " Cornelia Huck
2023-02-27 16:00   ` Parav Pandit
2023-02-27 16:00     ` [virtio-dev] " Parav Pandit
2023-02-27 17:33     ` Michael S. Tsirkin [this message]
2023-03-01 17:22   ` [virtio-dev] Re: [virtio-comment] " Halil Pasic
2023-03-01 17:37     ` Michael S. Tsirkin
2023-03-02 13:42       ` [virtio-dev] " Parav Pandit
2023-03-02 15:06       ` [virtio-dev] " Cornelia Huck
2023-03-02 15:58         ` Halil Pasic
2023-03-03  7:42         ` Michael S. Tsirkin
2023-03-03 21:49           ` Halil Pasic
2023-03-05  9:51             ` Michael S. Tsirkin
2023-03-09 16:46               ` Halil Pasic
2023-03-09 16:53                 ` Michael S. Tsirkin
2023-03-10 14:05                   ` Halil Pasic
2023-02-27 17:39 ` Michael S. Tsirkin
2023-02-27 17:39   ` [virtio-dev] " Michael S. Tsirkin
2023-03-02 15:52   ` [virtio-dev] Re: [virtio-comment] " Halil Pasic
2023-03-02 16:12     ` [virtio-dev] " Parav Pandit
2023-03-02 23:38       ` [virtio-dev] " Michael S. Tsirkin
2023-03-07 15:20         ` [virtio-dev] " Parav Pandit
2023-03-03 15:38       ` [virtio-dev] " Halil Pasic
2023-03-05  9:29         ` Michael S. Tsirkin

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=20230227123226-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=parav@nvidia.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