1From: Jeff Layton <jlayton@samba.org> 2Subject: Re: [RFC][PATCH 06/10] cifs: define inode-level cache object and 3 register them 4Date: Fri, 25 Jun 2010 18:26:51 -0400 5Lines: 30 6Message-ID: <20100625182651.36800d06@tlielax.poochiereds.net> 7References: <20100625125306.7f9b1966@tlielax.poochiereds.net> 8 <4C24A606.5040001@suse.de> 9 <1277220214-3597-1-git-send-email-sjayaraman@suse.de> <yes> 10 <9822.1277312573@redhat.com> <22697.1277470549@redhat.com> 11 <18628.1277502398@redhat.com> 12Mime-Version: 1.0 13Content-Type: text/plain; charset=US-ASCII 14Content-Transfer-Encoding: 7bit 15Cc: linux-cifs@vger.kernel.org, samba-technical@lists.samba.org, 16 linux-kernel@vger.kernel.org, Steve French <smfrench@gmail.com>, 17 linux-fsdevel@vger.kernel.org 18To: David Howells <dhowells@redhat.com> 19X-From: samba-technical-bounces@lists.samba.org Sat Jun 26 00:27:01 2010 20Return-path: <samba-technical-bounces@lists.samba.org> 21Envelope-to: gnsi-samba-technical@m.gmane.org 22Received: from fn.samba.org ([216.83.154.106] helo=lists.samba.org) 23 by lo.gmane.org with esmtp (Exim 4.69) 24 (envelope-from <samba-technical-bounces@lists.samba.org>) 25 id 1OSHMS-0003Yl-G8 26 for gnsi-samba-technical@m.gmane.org; Sat, 26 Jun 2010 00:27:01 +0200 27Received: from fn.samba.org (localhost [127.0.0.1]) 28 by lists.samba.org (Postfix) with ESMTP id 8919DAD2B8; 29 Fri, 25 Jun 2010 16:26:57 -0600 (MDT) 30X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on fn.samba.org 31X-Spam-Level: 32X-Spam-Status: No, score=-1.7 required=3.8 tests=AWL,BAYES_00,SPF_NEUTRAL 33 autolearn=no version=3.2.5 34X-Original-To: samba-technical@lists.samba.org 35Delivered-To: samba-technical@lists.samba.org 36Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com 37 [75.180.132.122]) 38 by lists.samba.org (Postfix) with ESMTP id ECB66AD220 39 for <samba-technical@lists.samba.org>; 40 Fri, 25 Jun 2010 16:26:51 -0600 (MDT) 41X-Authority-Analysis: v=1.0 c=1 a=iVNVO0OCT3kA:10 a=yQWWgrYGNuUA:10 42 a=kj9zAlcOel0A:10 a=20KFwNOVAAAA:8 a=hGzw-44bAAAA:8 43 a=AraS79FXNJ3kHilSTm4A:9 a=3STw0N-n4mJG0pydffwA:7 44 a=0uwppTlTaQ5HiYOalIavAxwTlvEA:4 a=CjuIK1q_8ugA:10 45 a=jEp0ucaQiEUA:10 a=dowx1zmaLagA:10 46X-Cloudmark-Score: 0 47X-Originating-IP: 71.70.153.3 48Received: from [71.70.153.3] ([71.70.153.3:55553] helo=mail.poochiereds.net) 49 by cdptpa-oedge01.mail.rr.com (envelope-from <jlayton@samba.org>) 50 (ecelerity 2.2.2.39 r()) with ESMTP 51 id 78/FA-24471-C2D252C4; Fri, 25 Jun 2010 22:26:53 +0000 52Received: from tlielax.poochiereds.net (tlielax.poochiereds.net [192.168.1.3]) 53 by mail.poochiereds.net (Postfix) with ESMTPS id 68F07580FA; 54 Fri, 25 Jun 2010 18:26:52 -0400 (EDT) 55In-Reply-To: <18628.1277502398@redhat.com> 56X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-redhat-linux-gnu) 57X-BeenThere: samba-technical@lists.samba.org 58X-Mailman-Version: 2.1.12 59Precedence: list 60List-Id: "Discussions on Samba internals. For general questions please 61 subscribe to the list samba@samba.org" 62 <samba-technical.lists.samba.org> 63List-Unsubscribe: <https://lists.samba.org/mailman/options/samba-technical>, 64 <mailto:samba-technical-request@lists.samba.org?subject=unsubscribe> 65List-Archive: <http://lists.samba.org/pipermail/samba-technical> 66List-Post: <mailto:samba-technical@lists.samba.org> 67List-Help: <mailto:samba-technical-request@lists.samba.org?subject=help> 68List-Subscribe: <https://lists.samba.org/mailman/listinfo/samba-technical>, 69 <mailto:samba-technical-request@lists.samba.org?subject=subscribe> 70Sender: samba-technical-bounces@lists.samba.org 71Errors-To: samba-technical-bounces@lists.samba.org 72Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/1003148> 73 74On Fri, 25 Jun 2010 22:46:38 +0100 75David Howells <dhowells@redhat.com> wrote: 76 77> Jeff Layton <jlayton@samba.org> wrote: 78> 79> > Looks like it mostly uses the ctime. IMO, the mtime would be a better 80> > choice since it changes less frequently, but I don't guess that it 81> > matters very much. 82> 83> I'd've thought mtime changes more frequently since that's altered when data is 84> written. ctime is changed when attributes are changed. 85> 86 87IIUC, updating mtime for a write is also an attribute change, and that 88affects ctime. According to the stat(2) manpage: 89 90 The field st_ctime is changed by writing or by setting inode informa- 91 tion (i.e., owner, group, link count, mode, etc.). 92 93> Note that Ext4 appears to have a file creation time field in its inode 94> (struct ext4_inode::i_crtime[_extra]). Can Samba be made to use that? 95> 96 97Is it exposed to userspace in any (standard) way? It would be handy to 98have that. While we're wishing...it might also be nice to have a 99standard way to get at the i_generation from userspace too. 100 101-- 102Jeff Layton <jlayton@samba.org> 103 104 105 106