From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: David Edmondson <david.edmondson@oracle.com>,
Heng Qi <hengqi@linux.alibaba.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
Alvaro Karsz <alvaro.karsz@solid-run.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Jason Wang <jasowang@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>
Subject: Re: [virtio-comment] [PATCH v10] virtio-net: support the virtqueue coalescing moderation
Date: Wed, 8 Mar 2023 12:25:00 -0500 [thread overview]
Message-ID: <20230308122332-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481A9D8A005A61139535CF7DCB49@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Mar 08, 2023 at 04:42:25PM +0000, Parav Pandit wrote:
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Monday, March 6, 2023 5:57 PM
> >
> > On Thu, Mar 02, 2023 at 11:36:18AM +0000, David Edmondson wrote:
> > > > + for an enabled transmit/receive virtqueue whose
> > number is \field{vqn}.
> > >
> > > Should this now be "whose index is \field{vqn}"?
> >
> > Ugh. I guess we'll have to fix the number/index mess in the spec first. Parav
> > you said you are looking into it?
>
> Yes, I want to send v1 for " Rename queue index to queue number" series.
> V1 will include,
>
> a. the vqn changes for net device rss and
> b. other ccw changes that Cornelia requested.
> c. extra note that you asked to add to mmio for referring the old naming convention
>
> I guess we agree that it should be vqn.
> Therefore, vq coalescing and aq series should progress with vqn terminology.
> This way all 3 series can progress in parallel (aq, vq coalescing, current spec cleanup).
Don't much care at this point but I think when I thought about this
deeply it seemed that yes, it is marginally better. Don't remember why
though ;)
--
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>,
Heng Qi <hengqi@linux.alibaba.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
Alvaro Karsz <alvaro.karsz@solid-run.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Jason Wang <jasowang@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>
Subject: [virtio-dev] Re: [virtio-comment] [PATCH v10] virtio-net: support the virtqueue coalescing moderation
Date: Wed, 8 Mar 2023 12:25:00 -0500 [thread overview]
Message-ID: <20230308122332-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481A9D8A005A61139535CF7DCB49@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Mar 08, 2023 at 04:42:25PM +0000, Parav Pandit wrote:
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Monday, March 6, 2023 5:57 PM
> >
> > On Thu, Mar 02, 2023 at 11:36:18AM +0000, David Edmondson wrote:
> > > > + for an enabled transmit/receive virtqueue whose
> > number is \field{vqn}.
> > >
> > > Should this now be "whose index is \field{vqn}"?
> >
> > Ugh. I guess we'll have to fix the number/index mess in the spec first. Parav
> > you said you are looking into it?
>
> Yes, I want to send v1 for " Rename queue index to queue number" series.
> V1 will include,
>
> a. the vqn changes for net device rss and
> b. other ccw changes that Cornelia requested.
> c. extra note that you asked to add to mmio for referring the old naming convention
>
> I guess we agree that it should be vqn.
> Therefore, vq coalescing and aq series should progress with vqn terminology.
> This way all 3 series can progress in parallel (aq, vq coalescing, current spec cleanup).
Don't much care at this point but I think when I thought about this
deeply it seemed that yes, it is marginally better. Don't remember why
though ;)
--
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-03-08 17:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 14:10 [virtio-dev] [PATCH v10] virtio-net: support the virtqueue coalescing moderation Heng Qi
2023-03-02 11:36 ` [virtio-dev] Re: [virtio-comment] " David Edmondson
2023-03-02 12:46 ` Heng Qi
2023-03-02 23:26 ` Michael S. Tsirkin
2023-03-06 22:57 ` Michael S. Tsirkin
2023-03-06 22:57 ` [virtio-dev] " Michael S. Tsirkin
2023-03-08 14:24 ` Heng Qi
2023-03-08 14:24 ` [virtio-dev] " Heng Qi
2023-03-08 16:42 ` Parav Pandit
2023-03-08 16:42 ` [virtio-dev] " Parav Pandit
2023-03-08 17:25 ` Michael S. Tsirkin [this message]
2023-03-08 17:25 ` [virtio-dev] " Michael S. Tsirkin
2023-03-02 14:48 ` [virtio-dev] " Parav Pandit
2023-03-02 23:34 ` [virtio-dev] " Michael S. Tsirkin
2023-03-07 14:36 ` [virtio-comment] " Parav Pandit
2023-03-07 14:36 ` [virtio-dev] " Parav Pandit
2023-03-03 3:26 ` Heng Qi
2023-03-08 22:30 ` [virtio-comment] " Parav Pandit
2023-03-08 22:30 ` Parav Pandit
2023-03-09 2:58 ` [virtio-comment] " Heng Qi
2023-03-09 2:58 ` [virtio-dev] " 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=20230308122332-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=david.edmondson@oracle.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.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 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.