From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: xen-devel@lists.xensource.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH v2] xen_disk: support "direct-io-safe" backend option
Date: Fri, 28 Jun 2013 18:26:15 +0200 [thread overview]
Message-ID: <51CDB927.80901@redhat.com> (raw)
In-Reply-To: <624B402D40D846D55A77B826@nimrod.local>
Il 28/06/2013 18:17, Alex Bligh ha scritto:
>
> But as Stefano says:
>
> --On 28 June 2013 11:56:29 +0100 Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
>
>> This is PV only, at least for the moment: emulated disks always use
>> writeback caching.
>> From the performance point of view, making this change for IDE disks is
>> not very important (because IDE is slow anyway).
>
> ... perhaps 'who cares'.
There are plenty of emulated devices that are not that slow, though
perhaps Xen management does not support them: AHCI, MegaSAS, VMware
pvscsi, and of course virtio-{blk,scsi}...
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: xen-devel@lists.xensource.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v2] xen_disk: support "direct-io-safe" backend option
Date: Fri, 28 Jun 2013 18:26:15 +0200 [thread overview]
Message-ID: <51CDB927.80901@redhat.com> (raw)
In-Reply-To: <624B402D40D846D55A77B826@nimrod.local>
Il 28/06/2013 18:17, Alex Bligh ha scritto:
>
> But as Stefano says:
>
> --On 28 June 2013 11:56:29 +0100 Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
>
>> This is PV only, at least for the moment: emulated disks always use
>> writeback caching.
>> From the performance point of view, making this change for IDE disks is
>> not very important (because IDE is slow anyway).
>
> ... perhaps 'who cares'.
There are plenty of emulated devices that are not that slow, though
perhaps Xen management does not support them: AHCI, MegaSAS, VMware
pvscsi, and of course virtio-{blk,scsi}...
Paolo
next prev parent reply other threads:[~2013-06-28 16:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 18:16 [Qemu-devel] [PATCH v2] xen_disk: support "direct-io-safe" backend option Stefano Stabellini
2013-06-27 18:16 ` Stefano Stabellini
2013-06-28 7:56 ` [Qemu-devel] " Paolo Bonzini
2013-06-28 7:56 ` Paolo Bonzini
2013-06-28 10:54 ` [Qemu-devel] " Ian Jackson
2013-06-28 10:54 ` Ian Jackson
2013-06-28 10:57 ` [Qemu-devel] " Stefano Stabellini
2013-06-28 10:57 ` Stefano Stabellini
2013-06-28 8:48 ` [Qemu-devel] " Alex Bligh
2013-06-28 8:48 ` Alex Bligh
2013-06-28 10:44 ` [Qemu-devel] " Ian Jackson
2013-06-28 10:44 ` Ian Jackson
2013-06-28 16:17 ` [Qemu-devel] " Alex Bligh
2013-06-28 16:17 ` Alex Bligh
2013-06-28 16:26 ` Paolo Bonzini [this message]
2013-06-28 16:26 ` Paolo Bonzini
2013-06-28 10:56 ` [Qemu-devel] " Stefano Stabellini
2013-06-28 10:56 ` Stefano Stabellini
2013-06-28 16:16 ` [Qemu-devel] " Stefano Stabellini
2013-06-28 16:51 ` George Dunlap
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=51CDB927.80901@redhat.com \
--to=pbonzini@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=alex@alex.org.uk \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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.