Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 28 Oct 2002 06:01:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 28 Oct 2002 06:01:50 -0500 Received: from ns.suse.de ([213.95.15.193]:17417 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id ; Mon, 28 Oct 2002 06:01:48 -0500 To: Jamie Lokier Cc: eggert@twinsun.com, linux-kernel@vger.kernel.org Subject: Re: nanosecond file timestamp resolution in filesystems, GNU make, etc. References: <20021027153651.GB26297@pimlott.net.suse.lists.linux.kernel> <200210280947.g9S9l9H01162@sic.twinsun.com.suse.lists.linux.kernel> <20021028102809.GA16062@bjl1.asuk.net.suse.lists.linux.kernel> From: Andi Kleen Date: 28 Oct 2002 12:08:07 +0100 In-Reply-To: Jamie Lokier's message of "28 Oct 2002 11:36:02 +0100" Message-ID: X-Mailer: Gnus v5.7/Emacs 20.6 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 773 Lines: 16 Jamie Lokier writes: > Unfortunately that application code breaks when the filesystem may > have timestamps with resolution better than 1 second, but worse than 1 > nanosecond. The current resolution is jiffies, which tends to be 1ms Then the application just can't do the right thing, > unless it knows what rounding was applied by the kernel/filesystem, so > it can change that rounding in a safe direction. The rounding is always truncation. So the application can just assume that. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/