From: Jason Wang <jasowang@redhat.com>
To: anthony@codemonkey.ws
Cc: krkumar2@in.ibm.com, kvm@vger.kernel.org, mst@redhat.com,
netdev@vger.kernel.org, rusty@rustcorp.com.au,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [RFC PATCH 0/2] Multiqueue support for qemu(virtio-net)
Date: Thu, 28 Apr 2011 11:11:41 +0800 [thread overview]
Message-ID: <19896.56045.886758.739747@gargle.gargle.HOWL> (raw)
In-Reply-To: <20110420082706.32157.59668.stgit@dhcp-91-7.nay.redhat.com.englab.nay.redhat.com>
Jason Wang writes:
> Inspired by Krishna's patch (http://www.spinics.net/lists/kvm/msg52098.html) and
> Michael's suggestions. The following series adds the multiqueue support for
> qemu and enable it for virtio-net (both userspace and vhost).
>
> The aim for this series is to simplified the management and achieve the same
> performacne with less codes.
>
> Follows are the differences between this series and Krishna's:
>
> - Add the multiqueue support for qemu and also for userspace virtio-net
> - Instead of hacking the vhost module to manipulate kthreads, this patch just
> implement the userspace based multiqueues and thus can re-use the existed vhost kernel-side codes without any modification.
> - Use 1:1 mapping between TX/RX pairs and vhost kthread because the
> implementation is based on usersapce.
> - The cli is also changed to make the mgmt easier, the -netdev option of qdev
> can now accpet more than one ids. You can start a multiqueue virtio-net device
> through:
> ./qemu-system-x86_64 -netdev tap,id=hn0,vhost=on,fd=X -netdev
> tap,id=hn0,vhost=on,fd=Y -device virtio-net-pci,netdev=hn0#hn1,queues=2 ...
>
Hi anthony:
Have any comments about this series (cli, codes, ...)?
Thanks.
> The series is very primitive and still need polished.
>
> Suggestions are welcomed.
> ---
>
> Jason Wang (2):
> net: Add multiqueue support
> virtio-net: add multiqueue support
>
>
> hw/qdev-properties.c | 37 ++++-
> hw/qdev.h | 3
> hw/vhost.c | 26 ++-
> hw/vhost.h | 1
> hw/vhost_net.c | 7 +
> hw/vhost_net.h | 2
> hw/virtio-net.c | 409 ++++++++++++++++++++++++++++++++------------------
> hw/virtio-net.h | 2
> hw/virtio-pci.c | 1
> hw/virtio.h | 1
> net.c | 34 +++-
> net.h | 15 +-
> 12 files changed, 353 insertions(+), 185 deletions(-)
>
> --
> Jason Wang
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-04-28 3:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 8:33 [Qemu-devel] [RFC PATCH 0/2] Multiqueue support for qemu(virtio-net) Jason Wang
2011-04-20 8:33 ` [Qemu-devel] [RFC PATCH 1/2] net: Add multiqueue support Jason Wang
2011-04-29 20:07 ` Anthony Liguori
2011-04-30 15:15 ` Jason Wang
2011-04-20 8:33 ` [Qemu-devel] [RFC PATCH 2/2] virtio-net: add " Jason Wang
2011-04-20 8:52 ` [Qemu-devel] [RFC PATCH 0/2] Multiqueue support for qemu(virtio-net) Krishna Kumar2
2011-04-21 3:33 ` Jason Wang
2011-04-29 20:10 ` Anthony Liguori
2011-04-30 14:55 ` Jason Wang
2011-04-28 3:11 ` Jason Wang [this message]
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=19896.56045.886758.739747@gargle.gargle.HOWL \
--to=jasowang@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=krkumar2@in.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).