Date: Fri, 27 May 2005 11:17:50 +0200 From: Marc Olzheim <marcolz@stack.nl> To: Ken Smith <kensmith@cse.Buffalo.EDU> Cc: freebsd-arch@freebsd.org Subject: Re: Modifying file access time upon exec... Message-ID: <20050527091750.GB91258@stack.nl> In-Reply-To: <1117139065.82793.20.camel@opus.cse.buffalo.edu> References: <1117139065.82793.20.camel@opus.cse.buffalo.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--61jdw2sOBCFtR2d/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, May 26, 2005 at 04:24:25PM -0400, Ken Smith wrote: > Any thoughts before I commit it? The patch itself is pretty small. But > given the sections of code it's mucking with combined with it adding a > little 'nit' filesystem implementers should be aware of I wanted to run > it by as many clueful eyes as possible before doing the final commit. Has this been run through some kind of real world performance test ? I can imagine for instance /bin/sh's vnode is being updated a lot... Would it be eligible to a becoming a mount option ? I don't see any real problems with it, but perhaps people running executables over NFS filesystems that cannot be mounted with noatime might have an issue, like netbooting diskless machines... Marc --61jdw2sOBCFtR2d/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCluW+ezjnobFOgrERAvQ6AJ94j17A3kxbnFee4Q/VpbGqciE9fwCfTBUK X56bUiy+sGLKQkcbpeHq5CE= =d4ZX -----END PGP SIGNATURE----- --61jdw2sOBCFtR2d/--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050527091750.GB91258>