From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: [PATCH 1/2] Btrfs: add datacow flag in inode flag Date: Tue, 15 Mar 2011 16:26:50 -0400 Message-ID: <1300220702-sup-5062@think> References: <4D6F52DE.5080508@cn.fujitsu.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Linux Btrfs , linux-fsdevel , hch@lst.de, "Theodore Tso" To: liubo Return-path: Received: from rcsinet10.oracle.com ([148.87.113.121]:25483 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756897Ab1COU1c (ORCPT ); Tue, 15 Mar 2011 16:27:32 -0400 In-reply-to: <4D6F52DE.5080508@cn.fujitsu.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Excerpts from liubo's message of 2011-03-03 03:35:42 -0500: > > For datacow control, the corresponding inode flags are needed. > This is for the following patch. > > Signed-off-by: Liu Bo > --- > include/linux/fs.h | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/include/linux/fs.h b/include/linux/fs.h > index 63d069b..bef47ff 100644 > --- a/include/linux/fs.h > +++ b/include/linux/fs.h > @@ -353,6 +353,8 @@ struct inodes_stat_t { > #define FS_TOPDIR_FL 0x00020000 /* Top of directory hierarchies*/ > #define FS_EXTENT_FL 0x00080000 /* Extents */ > #define FS_DIRECTIO_FL 0x00100000 /* Use direct i/o */ > +#define FS_NOCOW_FL 0x00800000 /* Do not cow file */ > +#define FS_COW_FL 0x01000000 /* Cow file */ > #define FS_RESERVED_FL 0x80000000 /* reserved for ext2 lib */ > > #define FS_FL_USER_VISIBLE 0x0003DFFF /* User visible flags */ Hi everyone, I'd like to go ahead and include these for btrfs to use. Are there objections or a different preferred interface? -chris