From owner-freebsd-arch@FreeBSD.ORG Fri Dec 19 19:48:04 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 03B9C3C9; Fri, 19 Dec 2014 19:48:04 +0000 (UTC) Received: from mx1.stack.nl (relay04.stack.nl [IPv6:2001:610:1108:5010::107]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mailhost.stack.nl", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BB7361C86; Fri, 19 Dec 2014 19:48:03 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id ACAB3B80AD; Fri, 19 Dec 2014 20:48:00 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id 9A7F228494; Fri, 19 Dec 2014 20:48:00 +0100 (CET) Date: Fri, 19 Dec 2014 20:48:00 +0100 From: Jilles Tjoelker To: Poul-Henning Kamp Subject: Re: Change default VFS timestamp precision? Message-ID: <20141219194800.GA29107@stack.nl> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <82135.1419010861@critter.freebsd.dk> User-Agent: Mutt/1.5.21 (2010-09-15) 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:48:04 -0000 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. -- Jilles Tjoelker