From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] virtio-scsi vs. virtio-blk
Date: Thu, 09 Aug 2012 17:41:31 +0200 [thread overview]
Message-ID: <5023DA2B.9020501@profihost.ag> (raw)
In-Reply-To: <5023B0C7.9050807@redhat.com>
OK VMs do work fine now. Sorry for missing the patch after switching to
qemu-kvm.
Am 09.08.2012 14:44, schrieb Paolo Bonzini:
> Ok, try deadline in the guest then. Using noop amplifies bad
> performance, because you lose request merging. With no host scheduler,
> as is the case with libiscsi, noop is rarely a good idea.
Tests with cache=none and deadline:
virtio-scsi:
write: io=8267MB, bw=94023KB/s, iops=23505, runt= 90032msec
read : io=14576MB, bw=165783KB/s, iops=41445, runt= 90035msec
write: io=21312MB, bw=240782KB/s, iops=58, runt= 90636msec
read : io=48072MB, bw=544882KB/s, iops=133, runt= 90342msec
virtio-blk:
write: io=9210MB, bw=104710KB/s, iops=26177, runt= 90070msec
read : io=18804MB, bw=213929KB/s, iops=53482, runt= 90006msec
write: io=29080MB, bw=329478KB/s, iops=80, runt= 90379msec
read : io=26328MB, bw=298159KB/s, iops=72, runt= 90421msec
So this looks OK to me. Do you agree? So with virtio-scsi discard should
work?
Greets and many thanks
Stefan
next prev parent reply other threads:[~2012-08-09 15:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 15:21 [Qemu-devel] virtio-scsi vs. virtio-blk Stefan Priebe
2012-08-08 16:17 ` Paolo Bonzini
2012-08-08 17:12 ` Stefan Priebe
2012-08-08 17:37 ` Paolo Bonzini
2012-08-09 6:13 ` Stefan Priebe
2012-08-09 7:01 ` Paolo Bonzini
2012-08-09 7:07 ` Stefan Priebe
2012-08-09 7:19 ` Paolo Bonzini
2012-08-09 7:41 ` Stefan Priebe
2012-08-09 7:53 ` Paolo Bonzini
2012-08-09 8:00 ` Stefan Priebe
2012-08-09 8:03 ` Paolo Bonzini
2012-08-09 9:18 ` Stefan Hajnoczi
2012-08-09 10:17 ` Stefan Priebe - Profihost AG
2012-08-09 11:04 ` Stefan Hajnoczi
2012-08-09 11:10 ` Paolo Bonzini
2012-08-09 11:24 ` Stefan Priebe - Profihost AG
2012-08-09 12:08 ` Stefan Priebe - Profihost AG
2012-08-09 12:19 ` Paolo Bonzini
2012-08-09 12:31 ` Stefan Priebe - Profihost AG
2012-08-09 12:44 ` Paolo Bonzini
2012-08-09 15:41 ` Stefan Priebe - Profihost AG [this message]
2012-08-09 12:52 ` ronnie sahlberg
2012-08-09 13:15 ` Paolo Bonzini
2012-08-09 13:39 ` Stefan Priebe - Profihost AG
2012-08-09 13:42 ` Paolo Bonzini
2012-08-09 13:52 ` Stefan Priebe - Profihost AG
2012-08-09 14:35 ` Paolo Bonzini
2012-08-09 14:25 ` Stefan Priebe - Profihost AG
2012-08-10 9:22 ` Stefan Priebe - Profihost AG
2012-08-10 10:20 ` Paolo Bonzini
2012-08-10 10:28 ` Stefan Priebe - Profihost AG
2012-08-10 10:30 ` Paolo Bonzini
2012-08-10 11:12 ` ronnie sahlberg
2012-08-10 11:57 ` Stefan Priebe - Profihost AG
2012-08-10 12:04 ` ronnie sahlberg
2012-08-10 12:14 ` Stefan Priebe - Profihost AG
2012-08-10 12:24 ` ronnie sahlberg
2012-08-10 12:35 ` Stefan Priebe - Profihost AG
2012-08-10 12:39 ` Paolo Bonzini
2012-08-10 12:43 ` Stefan Priebe - Profihost AG
2012-08-10 11:20 ` ronnie sahlberg
2012-08-10 11:54 ` Stefan Priebe - Profihost AG
2012-08-10 11:58 ` ronnie sahlberg
2012-08-10 12:38 ` Stefan Priebe - Profihost AG
2012-08-10 11:49 ` Stefan Priebe - Profihost AG
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=5023DA2B.9020501@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).