All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH] [RFC] qemu-upstream: add discard support for xen_disk
Date: Fri, 17 Jan 2014 17:06:53 +0100	[thread overview]
Message-ID: <20140117160653.GA20783@aepfle.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1401171540300.21510@kaball.uk.xensource.com>

On Fri, Jan 17, Stefano Stabellini wrote:

> Can't we just assume that if the backend can do discard on that file, it
> is simply going to enable feature-discard? Do we really need the
> toolstack driven option too?

If the backing file is fully ppopulated on purpose to avoid
fragmentation of that file, then silently enabling discard means the
unwanted fragmentation will occour over time. If anyone is really doing
that in their setup I certainly dont know. At least kvm/qemu has such
knob, and also an hyperv host offers sparse, fully populated and overlay
as possible option when creating a new virtual disk image.

Now I think that if libxl already writes feature-discard=0, qemu can use
that to clear BDRV_O_UNMAP. Also blkbk could be extended to first check
if the property already exists before blindly enabling discard. No idea
if that makes sense for "phy", but you never know.

Olaf

  reply	other threads:[~2014-01-17 16:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 22:01 [PATCH] [RFC] qemu-upstream: add discard support for xen_disk Olaf Hering
2014-01-10 10:02 ` Ian Campbell
2014-01-17 15:14 ` Stefano Stabellini
2014-01-17 15:29   ` Olaf Hering
2014-01-17 15:33     ` Stefano Stabellini
2014-01-17 15:38       ` Olaf Hering
2014-01-17 15:43         ` Stefano Stabellini
2014-01-17 16:06           ` Olaf Hering [this message]
2014-01-17 16:14             ` Stefano Stabellini
2014-01-17 16:19               ` Olaf Hering
2014-01-17 15:43         ` 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=20140117160653.GA20783@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=stefano.stabellini@eu.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.