From: Suresh Jayaraman Subject: Re: [RFC][PATCH 06/10] cifs: define inode-level cache object and register them Date: Fri, 25 Jun 2010 18:20:14 +0530 Lines: 24 Message-ID: <4C24A606.5040001@suse.de> References: <1277220214-3597-1-git-send-email-sjayaraman@suse.de> <9822.1277312573@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Steve French , linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: David Howells X-From: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Fri Jun 25 14:50:26 2010 Return-path: Envelope-to: glkc-linux-cifs-1dZseelyfdZg9hUCZPvPmw@public.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OS8MR-0007EU-OS for glkc-linux-cifs-1dZseelyfdZg9hUCZPvPmw@public.gmane.org; Fri, 25 Jun 2010 14:50:24 +0200 Received: (majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org) by vger.kernel.org via listexpand id S1754607Ab0FYMuX (ORCPT ); Fri, 25 Jun 2010 08:50:23 -0400 Received: from cantor2.suse.de ([195.135.220.15]:38716 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753675Ab0FYMuW (ORCPT ); Fri, 25 Jun 2010 08:50:22 -0400 Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.221.2]) by mx2.suse.de (Postfix) with ESMTP id B05E686A2E; Fri, 25 Jun 2010 14:50:21 +0200 (CEST) User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091130 SUSE/3.0.0-1.1.1 Thunderbird/3.0 In-Reply-To: <9822.1277312573-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Precedence: bulk List-ID: X-Mailing-List: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Archived-At: On 06/23/2010 10:32 PM, David Howells wrote: > Suresh Jayaraman wrote: > >> Define inode-level data storage objects (managed by cifsInodeInfo structs). >> Each inode-level object is created in a super-block level object and is >> itself a data storage object in to which pages from the inode are stored. >> >> The inode object is keyed by UniqueId. The coherency data being used is >> LastWriteTime and the file size. > > Isn't there a file creation time too? I think the creation time is currently being ignored as we won't be able to accomodate in POSIX stat struct. > I take it you don't support caching on files that are open for writing at this > time? > Yes. -- Suresh Jayaraman