All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: VM nocow, should VM software set +C by default?
Date: Wed, 26 Feb 2014 00:01:05 +0600	[thread overview]
Message-ID: <20140226000105.44b842e2@natsu> (raw)
In-Reply-To: <4C05BCCD-ED77-4D8D-B9C7-47CB6D1B4ACC@colorremedies.com>

[-- Attachment #1: Type: text/plain, Size: 682 bytes --]

On Tue, 25 Feb 2014 10:44:36 -0700
Chris Murphy <lists@colorremedies.com> wrote:

> the VM managing application needs to set +C on image files

It's a slippery slope, why not instigate that every program from now on has
to set +C on its user files? Or where do we stop, probably the browser should
also set +C on its user profile and cache files? How about the mail client for
the mail index? The torrent program on all temporary downloads?.. MySQL and
Postgres on all their databases?...

Insisting that every program now has to include a workaround for a
filesystem-specific gimmick does not seem to be a nice design decision
long-term.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2014-02-25 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 16:55 VM nocow, should VM software set +C by default? Chris Murphy
2014-02-21 17:56 ` Duncan
2014-02-25  9:16 ` Justin Ossevoort
2014-02-25 17:44   ` Chris Murphy
2014-02-25 17:53     ` Jim Salter
2014-02-25 18:33       ` Chris Murphy
2014-02-26  5:43         ` Duncan
2014-02-25 18:01     ` Roman Mamedov [this message]

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=20140226000105.44b842e2@natsu \
    --to=rm@romanrm.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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 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.