From owner-freebsd-arch@FreeBSD.ORG  Fri May 27 16:12:35 2005
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: freebsd-arch@freebsd.org
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 26F0616A41C
	for <freebsd-arch@freebsd.org>; Fri, 27 May 2005 16:12:35 +0000 (GMT)
	(envelope-from babkin@verizon.net)
Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F089D43D1D
	for <freebsd-arch@freebsd.org>; Fri, 27 May 2005 16:12:34 +0000 (GMT)
	(envelope-from babkin@verizon.net)
Received: from vms069.mailsrvcs.net ([192.168.1.2])
	by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix
	0.04 (built Dec 24 2004)) with ESMTPA id
	<0IH500KJ2P0YNRT6@vms046.mailsrvcs.net> for
	freebsd-arch@freebsd.org; Fri, 27 May 2005 11:12:34 -0500 (CDT)
Date: Fri, 27 May 2005 11:12:34 -0500 (CDT)
From: Sergey Babkin <babkin@verizon.net>
To: Marc Olzheim <marcolz@stack.nl>, Ken Smith <kensmith@cse.Buffalo.EDU>
Message-id: <15835986.1117210354543.JavaMail.root@vms069.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Cc: freebsd-arch@freebsd.org
Subject: Re: Re: Modifying file access time upon exec...
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2005 16:12:35 -0000

>No, I'm saying that there are filesystems you wouldn't want to mount
>with noatime (/tmp, /var/tmp, /var/mail, /var/spool/*) because some
>software depends on the atime being adjusted.
>
>But atime over NFS is something you'd usually want to turn off, because
>it can really hurt performance.

As a compromise, would it make sense to make the
atime granularity adjustable? I.e. instead of the 
default microsecond granularity use a 1-second 
granularity. Or a 10-second granularity, so that the 
atime would be adjusted only once per every 10 
seconds. And similarly for mtime, though here
you should obviously be more careful.

-SB