linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Wanlong Gao <gaowanlong@cn.fujitsu.com>,
	asias@redhat.com, mst@redhat.com,
	Rusty Russell <rusty@rustcorp.com.au>,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	linux-scsi@vger.kernel.org, JBottomley@parallels.com
Subject: [PATCH v3 0/5] virtio-scsi multiqueue
Date: Tue, 12 Feb 2013 14:06:26 +0100	[thread overview]
Message-ID: <1360674391-2661-1-git-send-email-pbonzini@redhat.com> (raw)

This series implements virtio-scsi queue steering, which gives
performance improvements of up to 50% (measured both with QEMU and
tcm_vhost backends).  The patches build on top of the new virtio APIs
at http://permalink.gmane.org/gmane.linux.kernel.virtualization/18431;
the new API simplifies the locking of the virtio-scsi driver nicely,
thus it makes sense to require them as a prerequisite.

Changes from the previous post, which can be found at
http://permalink.gmane.org/gmane.linux.kernel.virtualization/17869:

- patches 1 and 2 ("virtio: add functions for piecewise addition of
  buffers", "virtio-scsi: use functions for piecewise composition of
  buffers") split into their own series

- new cleanup patch "virtio-scsi: push vq lock/unlock into virtscsi_vq_done"

- reorganized code to move ACCESS_ONCE in a clearer place

- included Wanlong Gao's CPU hotplug patches

Ok for 3.9?  It would probably be easier to get it in via Rusty's tree
because of the prerequisites.  James, can I get your Acked-by?

Paolo

Paolo Bonzini (4):
  virtio-scsi: redo allocation of target data
  virtio-scsi: pass struct virtio_scsi to virtqueue completion function
  virtio-scsi: push vq lock/unlock into virtscsi_vq_done
  virtio-scsi: introduce multiqueue support

Wanlong Gao (1):
  virtio-scsi: reset virtqueue affinity when doing cpu hotplug

 drivers/scsi/virtio_scsi.c |  360 +++++++++++++++++++++++++++++++++++---------
 1 files changed, 292 insertions(+), 68 deletions(-)


             reply	other threads:[~2013-02-12 13:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 13:06 Paolo Bonzini [this message]
2013-02-12 13:06 ` [PATCH v3 1/5] virtio-scsi: redo allocation of target data Paolo Bonzini
2013-02-12 13:06 ` [PATCH v3 2/5] virtio-scsi: pass struct virtio_scsi to virtqueue completion function Paolo Bonzini
2013-02-12 13:06 ` [PATCH v3 3/5] virtio-scsi: push vq lock/unlock into virtscsi_vq_done Paolo Bonzini
2013-02-12 13:06 ` [PATCH v3 4/5] virtio-scsi: introduce multiqueue support Paolo Bonzini
2013-02-12 13:06 ` [PATCH v3 5/5] virtio-scsi: reset virtqueue affinity when doing cpu hotplug Paolo Bonzini
2013-02-18  9:32 ` [PATCH v3 0/5] virtio-scsi multiqueue Wanlong Gao
2013-02-18 10:05   ` Paolo Bonzini

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=1360674391-2661-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=JBottomley@parallels.com \
    --cc=asias@redhat.com \
    --cc=gaowanlong@cn.fujitsu.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --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).