From: Marc MERLIN <marc@merlins.org>
To: Filipe David Manana <fdmanana@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Filipe David Borba Manana <fdmanana@suse.com>
Subject: Re: NOCOW on VM images causes extreme btrfs slowdowns, memory leaks, and deadlocks
Date: Wed, 17 Sep 2014 10:13:22 -0700 [thread overview]
Message-ID: <20140917171322.GB29967@merlins.org> (raw)
In-Reply-To: <20140917150002.GA12223@merlins.org>
On Wed, Sep 17, 2014 at 08:00:02AM -0700, Marc MERLIN wrote:
> kernel: 3.16.2
Grumble, I messed up the subject line.
I meant that COW on virtual disk images causes the problems described in the
previous Email.
Obviously I already know that COW on disk images wasn't ideal, but the
effects in 3.16 are still fairly severe.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2014-09-17 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 1:51 btrfs differential receive has become excrutiatingly slow on one machine Marc MERLIN
2014-09-08 21:49 ` Filipe David Manana
2014-09-15 0:18 ` Marc MERLIN
2014-09-15 17:57 ` Marc MERLIN
2014-09-16 23:57 ` btrfs differential receive has become excrutiatingly slow with COW files Marc MERLIN
2014-09-17 15:00 ` NOCOW on VM images causes extreme btrfs slowdowns, memory leaks, and deadlocks Marc MERLIN
2014-09-17 17:13 ` Marc MERLIN [this message]
2015-05-11 21:44 ` btrfs differential receive has become excrutiatingly slow on one machine Marc MERLIN
2015-05-13 11:35 ` Filipe David Manana
2015-06-17 17:58 ` Marc MERLIN
2015-06-17 21:54 ` Marc MERLIN
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=20140917171322.GB29967@merlins.org \
--to=marc@merlins.org \
--cc=fdmanana@gmail.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.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.