From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Becker Subject: Re: [PATCH 1/3] fs: Document the reflink(2) system call. Date: Sun, 3 May 2009 19:46:12 -0700 Message-ID: <20090504024612.GB24653@mail.oracle.com> References: <1241331303-23753-1-git-send-email-joel.becker@oracle.com> <1241331303-23753-2-git-send-email-joel.becker@oracle.com> <20090503080112.GA27287@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, mtk.manpages@gmail.com, jmorris@namei.org, ocfs2-devel@oss.oracle.com, viro@zeniv.linux.org.uk To: Christoph Hellwig Return-path: Content-Disposition: inline In-Reply-To: <20090503080112.GA27287@infradead.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ocfs2-devel-bounces@oss.oracle.com Errors-To: ocfs2-devel-bounces@oss.oracle.com List-Id: linux-fsdevel.vger.kernel.org On Sun, May 03, 2009 at 04:01:12AM -0400, Christoph Hellwig wrote: > On Sat, May 02, 2009 at 11:15:01PM -0700, Joel Becker wrote: > > int reflink(const char *oldpath, const char *newpath); > > > > The reflink(2) system call creates reference-counted links. It creates > > a new file that shares the data extents of the source file in a > > copy-on-write fashion. Its calling semantics are identical to link(2). > > Once complete, programs see the new file as a completely separate entry. > > Just send this as a manpage to Michael, no need to duplicate a > pseudo-manpage in the kernel tree. The manpage style was just a convenient way to organize my thoughts. The goal was to document the behavior of reflink() for implementors. If the pseudo-manpage doesn't work, perhaps I'll try some other form. Joel -- Life's Little Instruction Book #337 "Reread your favorite book." Joel Becker Principal Software Developer Oracle E-mail: joel.becker@oracle.com Phone: (650) 506-8127