From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, kvm@vger.kernel.org, mst@redhat.com,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, pbonzini@redhat.com
Subject: Re: [PATCH V7 0/5] virtio-scsi multiqueue
Date: Sat, 06 Apr 2013 18:14:25 +0800 [thread overview]
Message-ID: <515FF581.5040403@cn.fujitsu.com> (raw)
In-Reply-To: <1365237613.2787.1.camel@dabdike>
On 04/06/2013 04:40 PM, James Bottomley wrote:
> On Fri, 2013-04-05 at 16:55 +0800, Wanlong Gao wrote:
>> On 03/28/2013 10:22 AM, Wanlong Gao wrote:
>>> On 03/23/2013 07:28 PM, Wanlong Gao wrote:
>>>> This series implements virtio-scsi queue steering, which gives
>>>> performance improvements of up to 50% (measured both with QEMU and
>>>> tcm_vhost backends).
>>>>
>>>> This version rebased on Rusty's virtio ring rework patches, which
>>>> has already gone into virtio-next today.
>>>> We hope this can go into virtio-next together with the virtio ring
>>>> rework pathes.
>>>>
>>>> V7: respin to fix the patch apply error
>>>>
>>>> V6: rework "redo allocation of target data" (James)
>>>> fix comments (Venkatesh)
>>>> rebase to virtio-next
>>>>
>>>> V5: improving the grammar of 1/5 (Paolo)
>>>> move the dropping of sg_elems to 'virtio-scsi: use virtqueue_add_sgs for command buffers'. (Asias)
>>>>
>>>> V4: rebase on virtio ring rework patches (rusty's pending-rebases branch)
>>>>
>>>> V3 and be found http://marc.info/?l=linux-virtualization&m=136067440717154&w=2
>>>>
>>>>
>>>> It would probably be easier to get it in via Rusty's tree
>>>> because of the prerequisites. James, can we get your Acked-by?
>>>
>>> James, any thoughts for this version?
>>
>> Ping James....
>
> Well, I haven't had time to look at anything other than the patch I
> commented on. I'm happy with your fix, so you can add my acked by to
> that one. Since it's going through the virtio tree, don't wait for me,
> put it in and I'll make you fix up anything I find later that I'm
> unhappy with.
Got it, thank you James.
Regards,
Wanlong Gao
>
> James
>
>
>
next prev parent reply other threads:[~2013-04-06 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 11:28 [PATCH V7 0/5] virtio-scsi multiqueue Wanlong Gao
2013-03-23 11:28 ` [PATCH V7 1/5] virtio-scsi: redo allocation of target data Wanlong Gao
2013-03-23 11:28 ` [PATCH V7 2/5] virtio-scsi: pass struct virtio_scsi to virtqueue completion function Wanlong Gao
2013-03-23 11:28 ` [PATCH V7 3/5] virtio-scsi: push vq lock/unlock into virtscsi_vq_done Wanlong Gao
2013-03-23 11:28 ` [PATCH V7 4/5] virtio-scsi: introduce multiqueue support Wanlong Gao
2013-03-25 7:25 ` Bart Van Assche
2013-03-25 14:27 ` Paolo Bonzini
2013-03-23 11:28 ` [PATCH V7 5/5] virtio-scsi: reset virtqueue affinity when doing cpu hotplug Wanlong Gao
2013-03-28 2:22 ` [PATCH V7 0/5] virtio-scsi multiqueue Wanlong Gao
2013-04-05 8:55 ` Wanlong Gao
2013-04-06 8:40 ` James Bottomley
2013-04-06 10:14 ` Wanlong Gao [this message]
2013-04-07 2:01 ` Asias He
2013-04-08 13:36 ` Rusty Russell
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=515FF581.5040403@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--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).