From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>, Andrey Korolyov <andrey@xdel.ru>,
Peter Lieven <pl@kamp.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Jeff Moyer <jmoyer@redhat.com>, Sergey Fionov <fionov@gmail.com>
Subject: Re: [Qemu-devel] 4k seq read splitting for virtio-blk - possible workarounds?
Date: Tue, 27 Oct 2015 10:30:27 +0100 [thread overview]
Message-ID: <562F4433.5080803@redhat.com> (raw)
In-Reply-To: <20151027020402.GB12940@ad.usersys.redhat.com>
On 27/10/2015 03:04, Fam Zheng wrote:
> > My plan is for
> > 2.6 to have fine-grained critical sections (patches written, will repost
> > during 2.5 hard freeze), 2.7 (unlikely 2.6) to have fine-grained locks,
> > and 2.8 or 2.9 to have multiqueue.
>
> You're talking about virtio-scsi, right? What about virtio-blk? Do you think we
> should resume the "fake" virtio-blk multiqueue work on QEMU side?
Even both. If you resume the "fake" virtio-blk multiqueue, converting
to real multiqueue at the same time as virtio-scsi should be trivial.
The difficult part of course is not the device models, it's the block
layer...
Paolo
next prev parent reply other threads:[~2015-10-27 9:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 11:50 [Qemu-devel] 4k seq read splitting for virtio-blk - possible workarounds? Andrey Korolyov
2015-10-26 15:37 ` Paolo Bonzini
2015-10-26 16:31 ` Andrey Korolyov
2015-10-26 16:37 ` Paolo Bonzini
2015-10-26 16:43 ` Andrey Korolyov
2015-10-26 17:03 ` Paolo Bonzini
2015-10-26 17:18 ` Andrey Korolyov
2015-10-26 17:32 ` Paolo Bonzini
2015-10-26 18:28 ` Andrey Korolyov
2015-10-27 2:04 ` Fam Zheng
2015-10-27 9:30 ` Paolo Bonzini [this message]
2015-10-30 20:04 ` Andrey Korolyov
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=562F4433.5080803@redhat.com \
--to=pbonzini@redhat.com \
--cc=andrey@xdel.ru \
--cc=axboe@kernel.dk \
--cc=famz@redhat.com \
--cc=fionov@gmail.com \
--cc=jmoyer@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.