From: "Michael S. Tsirkin" <mst@redhat.com>
To: Heng Qi <hengqi@linux.alibaba.com>
Cc: David Edmondson <david.edmondson@oracle.com>,
Alvaro Karsz <alvaro.karsz@solid-run.com>,
virtio-dev@lists.oasis-open.org, Parav Pandit <parav@nvidia.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Jason Wang <jasowang@redhat.com>,
virtio-comment@lists.oasis-open.org
Subject: [virtio-dev] Re: [virtio-comment] [PATCH v10] virtio-net: support the virtqueue coalescing moderation
Date: Thu, 2 Mar 2023 18:26:05 -0500 [thread overview]
Message-ID: <20230302182538-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <d7a008c0-3f93-5dfa-6897-8436bf30708c@linux.alibaba.com>
On Thu, Mar 02, 2023 at 08:46:03PM +0800, Heng Qi wrote:
> Have we decided yet, I see in Parav's thread it seems to be still under
> discussion? Michael should we be using index?
I don't know at this point. Maybe wait a bit more.
--
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-02 23:26 UTC|newest]
Thread overview: 14+ 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 [this message]
2023-03-06 22:57 ` Michael S. Tsirkin
2023-03-08 14:24 ` Heng Qi
2023-03-08 16:42 ` [virtio-dev] " Parav Pandit
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-dev] " Parav Pandit
2023-03-03 3:26 ` Heng Qi
2023-03-08 22:30 ` Parav Pandit
2023-03-09 2:58 ` [virtio-dev] Re: [virtio-comment] " 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=20230302182538-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox