From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Woodhouse Subject: Re: Proposal: Use hi-res clock for file timestamps Date: Wed, 18 Aug 2010 19:20:58 +0100 Message-ID: <1282155658.13405.36.camel@localhost> References: <87aaolwar8.fsf@basil.nowhere.org> <20100817174134.GA23176@fieldses.org> <20100817182920.GD18161@basil.fritz.box> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: "J. Bruce Fields" , "Patrick J. LoPresti" , linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel To: Andi Kleen Return-path: In-Reply-To: <20100817182920.GD18161-u0/ZJuX+froe6aEkudXLsA@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Tue, 2010-08-17 at 20:29 +0200, Andi Kleen wrote: > > > - Increment mtime by a nanosecond when necessary. > > You cannot be more precise than the backing file system: this causes > non monotonity when the inodes are flushed (has happened in the past) Um, can't you? You can't *store* timestamps which are more precise, but they can be in cache can't they? And since you're not going to drop it from cache and bring it back in again within 4ms, that ought to suffice? -- David Woodhouse Open Source Technology Centre David.Woodhouse-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org Intel Corporation -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html