[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.01.0909152116180.4950@localhost.localdomain>
Date: Tue, 15 Sep 2009 21:20:47 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Joel Becker <Joel.Becker@...cle.com>
cc: Mark Fasheh <mfasheh@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ocfs2-devel@....oracle.com
Subject: Re: [GIT PULL] ocfs2 changes for 2.6.32
On Tue, 15 Sep 2009, Joel Becker wrote:
>
> Perhaps ->copyfile takes the following flags:
>
> #define ALLOW_COW_SHARED 0x0001
> #define REQUIRE_COW_SHARED 0x0002
> #define REQUIRE_BASIC_ATTRS 0x0004
> #define REQUIRE_FULL_ATTRS 0x0008
> #define REQUIRE_ATOMIC 0x0010
> #define SNAPSHOT (REQUIRE_COW_SHARED |
> REQUIRE_BASIC_ATTRS |
> REQUIRE_ATOMIC)
> #define SNAPSHOT_PRESERVE (SNAPSHOT | REQUIRE_FULL_ATTRS)
>
> Thus, sys_reflink/sys_snapfile(oldpath, newpath, 0) becomes:
> ...
Yes. The above all sounds sane to me.
I still worry that especially the non-atomic case will want some kind of
partial-copy updates (think graphical file managers that want to show the
progress of the copy), and that (think EINTR and continuing) makes me
think "that could get really complex really quickly", but that's something
that the NFS/SMB people would have to pipe up on. I'm pretty sure the NFS
spec has some kind "partial completion notification" model, I dunno about
SMB.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists