From owner-freebsd-arch@FreeBSD.ORG Fri Dec 19 19:49:32 2014 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5FA7448B; Fri, 19 Dec 2014 19:49:32 +0000 (UTC) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 209EC1C9E; Fri, 19 Dec 2014 19:49:31 +0000 (UTC) Received: from critter.freebsd.dk (unknown [192.168.60.3]) by phk.freebsd.dk (Postfix) with ESMTP id CA1073BD1A; Fri, 19 Dec 2014 19:49:29 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.9/8.14.9) with ESMTP id sBJJnSMe082508; Fri, 19 Dec 2014 19:49:29 GMT (envelope-from phk@phk.freebsd.dk) To: Jilles Tjoelker Subject: Re: Change default VFS timestamp precision? In-reply-to: <20141219194800.GA29107@stack.nl> From: "Poul-Henning Kamp" References: <201412161348.41219.jhb@freebsd.org> <77322.1418933100@critter.freebsd.dk> <77371.1418933642@critter.freebsd.dk> <7567696.mqJ3jgzJgL@ralph.baldwin.cx> <82135.1419010861@critter.freebsd.dk> <20141219194800.GA29107@stack.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <82506.1419018568.1@critter.freebsd.dk> Date: Fri, 19 Dec 2014 19:49:28 +0000 Message-ID: <82507.1419018568@critter.freebsd.dk> Cc: "freebsd-arch@freebsd.org" , Adrian Chadd X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2014 19:49:32 -0000 -------- In message <20141219194800.GA29107@stack.nl>, Jilles Tjoelker writes: >On Fri, Dec 19, 2014 at 05:41:01PM +0000, Poul-Henning Kamp wrote: >> In message <7567696.mqJ3jgzJgL@ralph.baldwin.cx>, John Baldwin writes: > >> >Yes, and multiplication is cheaper than division. It's not a power of >> >two (so more than a single bitshift), but possibly in the noise compared >> >to the work in bintime() itself. > >> But why not use nanosecond resolution given that the cost is cheaper ? > >Because there is no API to set timestamps with nanosecond resolution, >and therefore a cp -p copy of a file will appear older than the original >with 99.9% probability. I think that is undesirable. Hmm, good point, I forgot about that screwup... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.