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

On Mon, 2015-01-12 at 10:15 +0100, Fabio Fantoni wrote:
> 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).

Stefano already corrected me on this in this very thread.

Ian.

  reply	other threads:[~2015-01-12  9:31 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
2015-01-12  9:31         ` Ian Campbell [this message]
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=1421055106.26317.0.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=fabio.fantoni@m2r.biz \
    --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.