Re: [PATCH V7 0/5] virtio-scsi multiqueue

From: Asias He
Date: Sat Apr 06 2013 - 22:02:00 EST


On Sat, Apr 06, 2013 at 09:40:13AM +0100, 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.

So, Rusty, could you pick this up in your virtio-next tree?

> James
>
>

--
Asias
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/