1 From: Steve French <smfrench@gmail.com>
2 Subject: Re: [RFC][PATCH 06/10] cifs: define inode-level cache object and
4 Date: Fri, 25 Jun 2010 18:05:30 -0500
6 Message-ID: <AANLkTilOTrHLvLv4XWYZO6xCnYZgYT7gO2M-oKZ6VvqM@mail.gmail.com>
7 References: <20100625125306.7f9b1966@tlielax.poochiereds.net>
8 <4C24A606.5040001@suse.de>
9 <1277220214-3597-1-git-send-email-sjayaraman@suse.de>
10 <9822.1277312573@redhat.com>
11 <22697.1277470549@redhat.com>
12 <18628.1277502398@redhat.com>
13 <20100625182651.36800d06@tlielax.poochiereds.net>
15 Content-Type: text/plain; charset=ISO-8859-1
16 Content-Transfer-Encoding: QUOTED-PRINTABLE
17 Cc: David Howells <dhowells@redhat.com>,
18 Suresh Jayaraman <sjayaraman@suse.de>,
19 linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
20 linux-kernel@vger.kernel.org, samba-technical@lists.samba.org,
21 Jeff Layton <jlayton@redhat.com>
22 To: Jeff Layton <jlayton@samba.org>,
23 "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
24 Mingming Cao <mcao@us.ibm.com>
25 X-From: linux-kernel-owner@vger.kernel.org Sat Jun 26 01:05:41 2010
26 Return-path: <linux-kernel-owner@vger.kernel.org>
27 Envelope-to: glk-linux-kernel-3@lo.gmane.org
28 Received: from vger.kernel.org ([209.132.180.67])
29 by lo.gmane.org with esmtp (Exim 4.69)
30 (envelope-from <linux-kernel-owner@vger.kernel.org>)
32 for glk-linux-kernel-3@lo.gmane.org; Sat, 26 Jun 2010 01:05:40 +0200
33 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
34 id S1756188Ab0FYXFd convert rfc822-to-quoted-printable (ORCPT
35 <rfc822;glk-linux-kernel-3@m.gmane.org>);
36 Fri, 25 Jun 2010 19:05:33 -0400
37 Received: from mail-qw0-f46.google.com ([209.85.216.46]:51369 "EHLO
38 mail-qw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
39 with ESMTP id S1751575Ab0FYXFb convert rfc822-to-8bit (ORCPT
40 <rfc822;linux-kernel@vger.kernel.org>);
41 Fri, 25 Jun 2010 19:05:31 -0400
42 Received: by qwi4 with SMTP id 4so742644qwi.19
43 for <multiple recipients>; Fri, 25 Jun 2010 16:05:30 -0700 (PDT)
44 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
46 h=domainkey-signature:mime-version:received:received:in-reply-to
47 :references:date:message-id:subject:from:to:cc:content-type
48 :content-transfer-encoding;
49 bh=6wKQkGOEeUGN4oPR3Nm4SRxtJr/EBwN8ENmpLnfdCDU=;
50 b=X7L6W0MtpQeW/4iBuj+oDlcP2yCJ3qwUs9lHBq1fRW6WdYblHXjmaN8o++3GDPLAg5
51 0MD07zxbYTGXRSrgCjCrGVm0tT88/6hY2a/rB8g68h/Qso2sIHa7B1iIN8JRR4pPWle0
52 sVjp9Xy/bQn2e0uE481Ii1TLHuWYA/QDXZreU=
53 DomainKey-Signature: a=rsa-sha1; c=nofws;
55 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
56 :cc:content-type:content-transfer-encoding;
57 b=B+7qQvdOpN5a/KCRrDbssKZX8D3SnP73VMHd9RpkqP9nCHCmSLAgbeH03+/m6CLVAo
58 G+NKWqWtknwPBkYqT/bdP2XEak1yr+0rjOqjUaNvaT7AhzsyHEJBkaNnsbS3qaRy39OP
59 S7OkAyHfmgdeNAHkKnKRF73hfpvgAqR9X4bn8=
60 Received: by 10.224.59.223 with SMTP id m31mr1130670qah.63.1277507130411; Fri,
61 25 Jun 2010 16:05:30 -0700 (PDT)
62 Received: by 10.229.46.136 with HTTP; Fri, 25 Jun 2010 16:05:30 -0700 (PDT)
63 In-Reply-To: <20100625182651.36800d06@tlielax.poochiereds.net>
64 Sender: linux-kernel-owner@vger.kernel.org
66 List-ID: <linux-kernel.vger.kernel.org>
67 X-Mailing-List: linux-kernel@vger.kernel.org
68 Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/1003154>
70 On Fri, Jun 25, 2010 at 5:26 PM, Jeff Layton <jlayton@samba.org> wrote:
72 > On Fri, 25 Jun 2010 22:46:38 +0100
73 > David Howells <dhowells@redhat.com> wrote:
75 > > Jeff Layton <jlayton@samba.org> wrote:
77 > > > Looks like it mostly uses the ctime. IMO, the mtime would be a be=
79 > > > choice since it changes less frequently, but I don't guess that i=
81 > > > matters very much.
83 > > I'd've thought mtime changes more frequently since that's altered w=
85 > > written. =A0ctime is changed when attributes are changed.
88 > IIUC, updating mtime for a write is also an attribute change, and tha=
90 > affects ctime. According to the stat(2) manpage:
92 > =A0 =A0 =A0 The field st_ctime is changed by writing or by setting =A0=
94 > =A0 =A0 =A0 tion (i.e., owner, group, link count, mode, etc.).
96 > > Note that Ext4 appears to have a file creation time field in its in=
98 > > (struct ext4_inode::i_crtime[_extra]). =A0Can Samba be made to use =
102 > Is it exposed to userspace in any (standard) way? It would be handy t=
104 > have that. While we're wishing...it might also be nice to have a
105 > standard way to get at the i_generation from userspace too.
108 Yes - I have talked with MingMing and Aneesh about those (NFS may
109 someday be able to use those too).=A0 An obstacle in the past had been
110 that samba server stores its own fake creation time in an ndr encoded
111 xattr which complicates things.
114 Xattr or other way to get at birth time?