From: Paolo Bonzini <pbonzini@redhat.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Subject: Re: [Qemu-devel] virtio-scsi vs. virtio-blk
Date: Thu, 09 Aug 2012 15:15:41 +0200 [thread overview]
Message-ID: <5023B7FD.6060306@redhat.com> (raw)
In-Reply-To: <CAN05THS22ybq77EyDKsPWE8zW_1u4F5XzKV3N3-DKF7DM-pu9w@mail.gmail.com>
Il 09/08/2012 14:52, ronnie sahlberg ha scritto:
>> >
>> > guest uses noop right now. Disk Host is nexentastor running open solaris. I
>> > use libiscsi right now so the disks are not visible in both cases
>> > (virtio-blk and virtio-scsi) to the host right now.
>> >
> And if you mount the disks locally on the host using open-iscsi, and
> access them as /dev/sg* from qemu, what performance do you get?
Good question.
> virtio-blk would first go to scsi emulation and then call out to
> block/iscsi.c to translate back to scsi commands to send to libiscsi
>
> while virtio-scsi (I think) would treat libiscsi as a generic scsi
> passthrough device. I.e. all commands just go straight through
> bdrv_aio_ioctl(SG_IO)
I think he's not using scsi-block or scsi-generic, because 1.0 libiscsi
didn't support that.
scsi-generic would indeed incur some overhead because it does not do
scatter/gather I/O directly, but scsi-hd/scsi-block do not have this
overhead. In any case, that should be visible through the output of
perf if it is significant.
Paolo
next prev parent reply other threads:[~2012-08-09 13:16 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
2012-08-09 12:52 ` ronnie sahlberg
2012-08-09 13:15 ` Paolo Bonzini [this message]
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=5023B7FD.6060306@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=s.priebe@profihost.ag \
--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).