public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: nirbheek@gentoo.org, rich0@gentoo.org
Subject: Re: [gentoo-dev] Re: proj/portage:master commit in: pym/portage/dbapi/
Date: Sat, 26 Nov 2011 17:08:31 +0100	[thread overview]
Message-ID: <20111126170831.16d9d656@pomiocik.lan> (raw)
In-Reply-To: <CADqQcK4g_QaZK-VuK6D3Y5=S_5jVhEPo64XPGVx36=ZopMQHbA@mail.gmail.com>

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

On Sat, 26 Nov 2011 21:28:51 +0530
Nirbheek Chauhan <nirbheek@gentoo.org> wrote:

> On Sat, Nov 26, 2011 at 8:39 PM, Michał Górny <mgorny@gentoo.org>
> wrote:
> > But in this particular case, I don't think COW is particularly
> > useful. If it works only on filesystem bounds, we could move the
> > file directly anyway.
> >
> 
> There are still a few specific cases in which CoW would indeed be
> useful. IIRC, reflinking of files works across btrfs *subvolumes*, and
> such a copy would normally be detected as a cross-device move.

For such a thing, shouldn't rename() work neat anyway?

> Another use would be an patch-merge which makes use of *ranged
> reflinks* to only CoW copy those parts of the file that were
> changed[1]. rsync has support for this, but only while appending to
> files (--append-verify --no-whole-file).

So, it'd be like:
1) CoW-dup old file,
2) patch-merge into the duped old file,
3) replace.

Am I understanding correctly?

-- 
Best regards,
Michał Górny

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

  reply	other threads:[~2011-11-26 16:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1d4ac47c28706094230cb2c4e6ee1c1c71629aa0.arfrever@gentoo>
2011-11-26 10:58 ` [gentoo-dev] Re: proj/portage:master commit in: pym/portage/dbapi/ Fabian Groffen
2011-11-26 11:26   ` Nirbheek Chauhan
2011-11-26 11:37     ` "Paweł Hajdan, Jr."
     [not found]     ` <20111126113830.GC37825@gentoo.org>
2011-11-26 12:50       ` Nirbheek Chauhan
2011-11-26 12:59         ` Ciaran McCreesh
2011-11-26 13:44           ` Rich Freeman
2011-11-26 15:09             ` Michał Górny
2011-11-26 15:25               ` Rich Freeman
2011-11-26 16:00                 ` Michał Górny
2011-11-26 15:58               ` Nirbheek Chauhan
2011-11-26 16:08                 ` Michał Górny [this message]
2011-11-26 16:31                   ` Nirbheek Chauhan
2011-11-26 15:50             ` Nirbheek Chauhan
2011-11-26 16:19         ` Mike Frysinger
2011-11-26 16:34           ` Nirbheek Chauhan
2011-11-27 21:44           ` [gentoo-portage-dev] " Zac Medico
2011-11-27 22:28   ` Arfrever Frehtes Taifersar Arahesis
2011-11-28  8:06     ` Michał Górny
2011-11-28 12:57       ` Rich Freeman
2011-11-30 20:31     ` Mike Frysinger

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=20111126170831.16d9d656@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=nirbheek@gentoo.org \
    --cc=rich0@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox