All of lore.kernel.org
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Parav Pandit <parav@nvidia.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>,
	Halil Pasic <pasic@linux.ibm.com>
Subject: [virtio-comment] Re: [virtio-dev] RE: [virtio-comment] [PATCH v14 04/11] transport-pci: Avoid first vq index reference
Date: Tue, 25 Apr 2023 18:20:08 +0200	[thread overview]
Message-ID: <20230425182008.707b3b56.pasic@linux.ibm.com> (raw)
In-Reply-To: <20230425091058-mutt-send-email-mst@kernel.org>

On Tue, 25 Apr 2023 09:15:14 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Tue, Apr 25, 2023 at 03:02:15PM +0200, Halil Pasic wrote:
> > On Tue, 25 Apr 2023 04:10:00 +0000
> > Parav Pandit <parav@nvidia.com> wrote:
[..]
> > > Sure. All you wrote is correct.
> > >   
> > 
> > I'm happy we agree. All I say we may want to rewrite the 
> > 
> > "Each virtqueue is identified by a virtqueue index; virtqueue index
> > range is from 0 to 65535 inclusive."
> > as
> > "Each virtqueue is uniquely identified by a virtqueue index. The number
> > of supported virtqueues is device dependent, but can never exceed 65536.
> > Thus 16 bit is sufficient to represent virtqueue indexes. If the number
> > of virtqueues currently supported by some device is N, each of it is
> > virtqueues is uniquely identified by a single index from the range
> > [0..N-1]."  
> 
> Seems to be repeating same thing over and over.

Nod.

> This redundancy has cost, e.g. more places to change when we
> talk about admin queues.
> Yes it can not be any number 0 to 65535 but this kind of nitpicking
> belongs in conformance statements not in general description.
> 

I tend to agree. I would prefer to have it in some sort of conformance
statement, but I would also prefer to have it in exactly one place (and
not all over the place).

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/


WARNING: multiple messages have this Message-ID (diff)
From: Halil Pasic <pasic@linux.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Parav Pandit <parav@nvidia.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>,
	Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [virtio-dev] RE: [virtio-comment] [PATCH v14 04/11] transport-pci: Avoid first vq index reference
Date: Tue, 25 Apr 2023 18:20:08 +0200	[thread overview]
Message-ID: <20230425182008.707b3b56.pasic@linux.ibm.com> (raw)
In-Reply-To: <20230425091058-mutt-send-email-mst@kernel.org>

On Tue, 25 Apr 2023 09:15:14 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Tue, Apr 25, 2023 at 03:02:15PM +0200, Halil Pasic wrote:
> > On Tue, 25 Apr 2023 04:10:00 +0000
> > Parav Pandit <parav@nvidia.com> wrote:
[..]
> > > Sure. All you wrote is correct.
> > >   
> > 
> > I'm happy we agree. All I say we may want to rewrite the 
> > 
> > "Each virtqueue is identified by a virtqueue index; virtqueue index
> > range is from 0 to 65535 inclusive."
> > as
> > "Each virtqueue is uniquely identified by a virtqueue index. The number
> > of supported virtqueues is device dependent, but can never exceed 65536.
> > Thus 16 bit is sufficient to represent virtqueue indexes. If the number
> > of virtqueues currently supported by some device is N, each of it is
> > virtqueues is uniquely identified by a single index from the range
> > [0..N-1]."  
> 
> Seems to be repeating same thing over and over.

Nod.

> This redundancy has cost, e.g. more places to change when we
> talk about admin queues.
> Yes it can not be any number 0 to 65535 but this kind of nitpicking
> belongs in conformance statements not in general description.
> 

I tend to agree. I would prefer to have it in some sort of conformance
statement, but I would also prefer to have it in exactly one place (and
not all over the place).

Regards,
Halil

[..]

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


  reply	other threads:[~2023-04-25 16:20 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19  1:46 [virtio-comment] [PATCH v14 00/11] Rename queue number to queue index Parav Pandit
2023-04-19  1:46 ` [virtio-dev] " Parav Pandit
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 01/11] content: Add vq index text Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 02/11] content.tex Replace virtqueue number with index Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-19 16:08   ` [virtio-comment] " Halil Pasic
2023-04-19 16:08     ` [virtio-dev] " Halil Pasic
2023-04-19 16:11     ` [virtio-comment] " Parav Pandit
2023-04-19 16:11       ` [virtio-dev] " Parav Pandit
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 03/11] content: Rename confusing queue_notify_data and vqn names Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-21 22:37   ` [virtio-comment] " Halil Pasic
2023-04-21 22:37     ` [virtio-dev] " Halil Pasic
2023-04-24 14:00     ` [virtio-comment] " Michael S. Tsirkin
2023-04-24 14:00       ` [virtio-dev] " Michael S. Tsirkin
2023-04-24 16:11     ` [virtio-comment] " Parav Pandit
2023-04-24 16:11       ` [virtio-dev] " Parav Pandit
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 04/11] transport-pci: Avoid first vq index reference Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-24 13:29   ` [virtio-comment] " Halil Pasic
2023-04-24 13:29     ` [virtio-dev] " Halil Pasic
2023-04-25  4:10     ` Parav Pandit
2023-04-25  4:10       ` [virtio-dev] " Parav Pandit
2023-04-25 13:02       ` [virtio-comment] " Halil Pasic
2023-04-25 13:02         ` Halil Pasic
2023-04-25 13:15         ` [virtio-comment] " Michael S. Tsirkin
2023-04-25 13:15           ` Michael S. Tsirkin
2023-04-25 16:20           ` Halil Pasic [this message]
2023-04-25 16:20             ` Halil Pasic
2023-04-25 21:11             ` [virtio-comment] " Michael S. Tsirkin
2023-04-25 21:11               ` Michael S. Tsirkin
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 05/11] transport-mmio: Rename QueueNum register Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-24 12:53   ` [virtio-comment] " Halil Pasic
2023-04-24 12:53     ` Halil Pasic
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 06/11] transport-mmio: Avoid referring to zero based index Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-25 10:59   ` [virtio-comment] " Halil Pasic
2023-04-25 10:59     ` [virtio-dev] " Halil Pasic
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 07/11] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-24 12:58   ` [virtio-comment] " Halil Pasic
2023-04-24 12:58     ` Halil Pasic
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 08/11] transport-ccw: Refer to the vq by its index Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 09/11] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-24 13:10   ` [virtio-comment] " Halil Pasic
2023-04-24 13:10     ` Halil Pasic
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 10/11] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-24 13:22   ` [virtio-comment] " Halil Pasic
2023-04-24 13:22     ` [virtio-dev] " Halil Pasic
2023-04-24 13:58     ` [virtio-comment] " Michael S. Tsirkin
2023-04-24 13:58       ` [virtio-dev] " Michael S. Tsirkin
2023-04-24 15:30       ` [virtio-comment] " Parav Pandit
2023-04-24 15:30         ` [virtio-dev] " Parav Pandit
2023-04-24 15:54         ` [virtio-comment] " Michael S. Tsirkin
2023-04-24 15:54           ` [virtio-dev] " Michael S. Tsirkin
2023-04-24 16:02           ` [virtio-comment] " Parav Pandit
2023-04-24 16:02             ` [virtio-dev] " Parav Pandit
2023-04-19  1:46 ` [virtio-comment] [PATCH v14 11/11] virtio-net: Update vqn to vq_index for cvq cmds Parav Pandit
2023-04-19  1:46   ` [virtio-dev] " Parav Pandit
2023-04-24 13:26   ` [virtio-comment] " Halil Pasic
2023-04-24 13:26     ` Halil Pasic

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=20230425182008.707b3b56.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 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.