From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "Michael S.Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>, krkumar2 <krkumar2@in.ibm.com>,
mashirle <mashirle@us.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] [question] one vhost kthread servers mulitiple tx/rx queues which blong to one virtio-net device
Date: Fri, 22 Aug 2014 10:30:32 +0800 [thread overview]
Message-ID: <201408221030300908823@sangfor.com> (raw)
Hi, Krishna, Shirley
How got get the latest patch of M:N Implementation of mulitiqueue,
I am going to test the the combination of "M:N Implementation of mulitiqueue" and "vhost: add polling mode".
Thanks,
Zhang Haoyu
next reply other threads:[~2014-08-22 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 2:30 Zhang Haoyu [this message]
2014-08-22 7:34 ` [Qemu-devel] [question] one vhost kthread servers mulitiple tx/rx queues which blong to one virtio-net device Jason Wang
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=201408221030300908823@sangfor.com \
--to=zhanghy@sangfor.com \
--cc=jasowang@redhat.com \
--cc=krkumar2@in.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mashirle@us.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).