From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [RFC PATCH 0/3] Sharing MSIX irq for tx/rx queue pairs
Date: Sun, 28 Dec 2014 09:52:26 +0200 [thread overview]
Message-ID: <20141228075226.GA25704@redhat.com> (raw)
In-Reply-To: <1419562425-20614-1-git-send-email-jasowang@redhat.com>
On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote:
> Hi all:
>
> This series try to share MSIX irq for each tx/rx queue pair. This is
> done through:
>
> - introducing virtio pci channel which are group of virtqueues that
> sharing a single MSIX irq (Patch 1)
> - expose channel setting to virtio core api (Patch 2)
> - try to use channel setting in virtio-net (Patch 3)
>
> For the transport that does not support channel, channel paramters
> were simply ignored. For devices that does not use channel, it can
> simply pass NULL or zero to virito core.
>
> With the patch, 1 MSIX irq were saved for each TX/RX queue pair.
>
> Please review.
How does this sharing affect performance?
> Thanks
>
> Jason Wang (3):
> virtio-pci: introduce channels
> virtio: let vp_find_vqs accept channel setting paramters
> virtio-net: using single MSIX irq for each TX/RX queue pair
>
> drivers/block/virtio_blk.c | 3 +-
> drivers/char/virtio_console.c | 3 +-
> drivers/lguest/lguest_device.c | 5 +-
> drivers/misc/mic/card/mic_virtio.c | 5 +-
> drivers/net/caif/caif_virtio.c | 3 +-
> drivers/net/virtio_net.c | 26 ++++-
> drivers/remoteproc/remoteproc_virtio.c | 5 +-
> drivers/rpmsg/virtio_rpmsg_bus.c | 3 +-
> drivers/s390/kvm/kvm_virtio.c | 5 +-
> drivers/s390/kvm/virtio_ccw.c | 5 +-
> drivers/scsi/virtio_scsi.c | 3 +-
> drivers/virtio/virtio_balloon.c | 3 +-
> drivers/virtio/virtio_mmio.c | 5 +-
> drivers/virtio/virtio_pci_common.c | 207 ++++++++++++++++++++-------------
> drivers/virtio/virtio_pci_common.h | 19 ++-
> include/linux/virtio_config.h | 8 +-
> 16 files changed, 208 insertions(+), 100 deletions(-)
>
> --
> 1.8.3.1
next prev parent reply other threads:[~2014-12-28 7:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 2:53 [RFC PATCH 0/3] Sharing MSIX irq for tx/rx queue pairs Jason Wang
2014-12-26 2:53 ` [RFC PATCH 1/3] virtio-pci: introduce channels Jason Wang
2014-12-26 2:53 ` [RFC PATCH 2/3] virtio: let vp_find_vqs accept channel setting paramters Jason Wang
2014-12-26 2:53 ` [RFC PATCH 3/3] virtio-net: using single MSIX irq for each TX/RX queue pair Jason Wang
2014-12-26 10:17 ` Jason Wang
2014-12-28 7:52 ` Michael S. Tsirkin [this message]
2015-01-04 8:38 ` [RFC PATCH 0/3] Sharing MSIX irq for tx/rx queue pairs Jason Wang
2015-01-04 11:36 ` Michael S. Tsirkin
2015-01-05 3:09 ` Jason Wang
2015-01-05 1:39 ` Rusty Russell
2015-01-05 5:10 ` 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=20141228075226.GA25704@redhat.com \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).