From: Kevin Wolf <kwolf@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Chunyan Liu <cyliu@suse.com>, stefanha@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img: set nocow flag to new file
Date: Thu, 14 Nov 2013 11:14:39 +0100 [thread overview]
Message-ID: <20131114101439.GB9755@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <p1iovvxqph.fsf@linaro.org>
Am 14.11.2013 um 10:44 hat Alex Bennée geschrieben:
>
> cyliu@suse.com writes:
>
> > Set NOCOW flag to newly created images to solve performance issues on btrfs.
> >
> > Btrfs has terrible performance when hosting VM images, even more when the guest
> > in those VM are also using btrfs as file system. One way to mitigate this bad
> > performance is to turn off COW attributes on VM files (since having copy on
> > write for this kind of data is not useful).
> <snip>
>
> It's been a while since I had to mess with this performance mystery but
> I recall you also need to ensure the partition needs to be mounted with
> the nodatacow mount option. Unless this has changed we should probably
> warn the user about that.
>From the information I read today while looking at this patch, the
nodatacow mount option seems just to influence the default for newly
created files. That is, if you set the flag like this patch is doing,
it has the same effect as running qemu-img create while having mounted
the file system with nodatacow.
Never tried it on my own, though, so take it with a grain of salt.
Kevin
next prev parent reply other threads:[~2013-11-14 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 8:15 [Qemu-devel] [PATCH] qemu-img: set nocow flag to new file Chunyan Liu
2013-11-14 9:17 ` Kevin Wolf
2013-11-14 14:23 ` Alex Bligh
2013-11-14 14:28 ` Alex Bligh
2013-11-15 4:05 ` Chunyan Liu
2013-11-15 12:26 ` Kevin Wolf
2013-11-14 9:44 ` Alex Bennée
2013-11-14 10:14 ` Kevin Wolf [this message]
2013-11-15 9:38 ` Stefan Hajnoczi
2013-11-18 4:54 ` Chunyan Liu
2013-11-18 9:57 ` Stefan Hajnoczi
2013-12-10 22:23 ` Alex Bennée
2013-12-11 8:29 ` Stefan Hajnoczi
2013-12-18 14:24 ` Daniel P. Berrange
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=20131114101439.GB9755@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cyliu@suse.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).