From: Paolo Bonzini <pbonzini@redhat.com>
To: kkv@clodo.ru, Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio-blk and virtio-scsi performance comparison
Date: Tue, 21 Apr 2015 11:57:33 +0200 [thread overview]
Message-ID: <55361F0D.9040907@redhat.com> (raw)
In-Reply-To: <55361E1C.7040302@clodo.ru>
On 21/04/2015 11:53, Konstantin Krotov wrote:
>> Can you detail the problem more? That could be a kernel bug.
>
> I connect to the host system, two storage systems as block devices. Both
> block devices combine md-raid1. md-device use as disk for virtual
> machine. If i use io=native, read perform only from one of two raid1
> legs. I'd like to distribute the load reading between two raid1 legs,
> but md-raid1 implementation it does only if set io=thread.
That looks like a kernel problem.
Paolo
prev parent reply other threads:[~2015-04-21 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 8:17 [Qemu-devel] virtio-blk and virtio-scsi performance comparison Konstantin Krotov
2015-04-16 1:27 ` Fam Zheng
2015-04-16 8:04 ` Paolo Bonzini
2015-04-16 11:17 ` Konstantin Krotov
2015-04-16 11:57 ` Paolo Bonzini
2015-04-21 9:53 ` Konstantin Krotov
2015-04-21 9:57 ` Paolo Bonzini [this message]
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=55361F0D.9040907@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kkv@clodo.ru \
--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 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).