All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Dario Faggioli <dario.faggioli@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
	xen-devel@lists.xen.org,
	"Ian Jackson" <ian.jackson@eu.citrix.com>,
	"Ian Campbell" <ian.campbell@citrix.com>,
	"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH resend] libxl, hotplug/Linux: default to phy backend for raw format file, take 2
Date: Mon, 12 Jan 2015 10:15:09 +0100	[thread overview]
Message-ID: <54B3909D.1040102@m2r.biz> (raw)
In-Reply-To: <1420825136.13270.45.camel@Abyss.station>

Il 09/01/2015 18:38, Dario Faggioli ha scritto:
> On Fri, 2015-01-09 at 14:42 +0000, Wei Liu wrote:
>> On Thu, Jan 08, 2015 at 03:33:17PM +0100, Fabio Fantoni wrote:
>>> Sorry for the probably stupid question, what are the pros and cons of
>>> default use of phy instead qdisk for raw files as domU disk?
>>>
>> There's no stupid question. :-)
>>
>> I was told that it performs better and enables other potential
>> improvements.
>>
> Not a big deal, probably, but IMO it would be nice to have at least a
> few words about when it's happening in the changelog, wouldn't it?

I'm also interested in detailed changelog about.

In the meantime, I saw this:
http://lists.xen.org/archives/html/xen-users/2015-01/msg00047.html
Based on the post above seems that phy will have important risk of data 
loss if I understand good, from Ian Campbell post:
> xl also uses qdisk for raw disk images instead of loop+blkback which
> xend used, because there are concerns that the loop driver can lead to
> data loss (by not implementing direct i/o the underlying device, and/or
> not handling flushes correct, my memory is a bit fuzzy).

Thanks for any reply and sorry for my bad english.


>
> Regards,
> Dario
>

  reply	other threads:[~2015-01-12  9:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 13:46 [PATCH resend] libxl, hotplug/Linux: default to phy backend for raw format file, take 2 Wei Liu
2015-01-08 14:08 ` Ian Campbell
2015-01-08 14:33 ` Fabio Fantoni
2015-01-09 14:42   ` Wei Liu
2015-01-09 17:38     ` Dario Faggioli
2015-01-12  9:15       ` Fabio Fantoni [this message]
2015-01-12  9:31         ` Ian Campbell
2015-01-12  9:39           ` Fabio Fantoni
2015-01-12 10:06             ` Ian Campbell
2015-01-12 10:17               ` Fabio Fantoni
2015-01-12 10:18                 ` Ian Campbell

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=54B3909D.1040102@m2r.biz \
    --to=fabio.fantoni@m2r.biz \
    --cc=dario.faggioli@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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.