From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51876) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZEbo2-0006Vy-47 for qemu-devel@nongnu.org; Mon, 13 Jul 2015 07:21:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZEbnw-000596-Mh for qemu-devel@nongnu.org; Mon, 13 Jul 2015 07:21:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47080) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZEbnw-000592-G7 for qemu-devel@nongnu.org; Mon, 13 Jul 2015 07:21:48 -0400 Date: Mon, 13 Jul 2015 14:21:44 +0300 From: "Michael S. Tsirkin" Message-ID: <20150713141421-mutt-send-email-mst@redhat.com> References: <20150702012121.GA4477@ad.nay.redhat.com> <20150708173423-mutt-send-email-mst@redhat.com> <20150709132248.GA12399@stefanha-thinkpad.redhat.com> <20150709162723-mutt-send-email-mst@redhat.com> <55A39047.5070806@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55A39047.5070806@redhat.com> Subject: Re: [Qemu-devel] virtio-blk multiqueue support in qemu. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Naredula Janardhana Reddy , Fam Zheng , Stefan Hajnoczi , Ming Lei , qemu-devel@nongnu.org, Stefan Hajnoczi On Mon, Jul 13, 2015 at 12:17:43PM +0200, Paolo Bonzini wrote: > > > On 09/07/2015 15:29, Michael S. Tsirkin wrote: > > > On the positive side, we do need something similar to the last 3 patches > > > to expose multiqueue to the guest. But it will require much more work > > > in QEMU to achieve true multiqueue. > > > > Might this be useful as an intermediate step, e.g. for testing > > guest code? > > Yes, this is already how virtio-scsi multiqueue is implemented. The > speedup is noticeable. However, for virtio-blk there is a huge > consumption of interrupt vectors in the guest, so it doesn't scale to > multiple disks as well as virtio-scsi. Could you elaborate please? interrupt vector usage is generally up to the guest, so whatever the issue is might be fixable by driver changes alone. -- MST