From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 1/3] fs: Document the reflink(2) system call. Date: Sun, 3 May 2009 04:01:12 -0400 Message-ID: <20090503080112.GA27287@infradead.org> References: <1241331303-23753-1-git-send-email-joel.becker@oracle.com> <1241331303-23753-2-git-send-email-joel.becker@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, jmorris@namei.org, ocfs2-devel@oss.oracle.com, viro@zeniv.linux.org.uk, mtk.manpages@gmail.com To: Joel Becker Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:42093 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751883AbZECIBL (ORCPT ); Sun, 3 May 2009 04:01:11 -0400 Content-Disposition: inline In-Reply-To: <1241331303-23753-2-git-send-email-joel.becker@oracle.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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.