lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 18 Aug 2010 14:54:56 -0400 From: "J. Bruce Fields" <bfields@...ldses.org> To: Andi Kleen <andi@...stfloor.org> Cc: Neil Brown <neilb@...e.de>, Alan Cox <alan@...rguk.ukuu.org.uk>, "Patrick J. LoPresti" <lopresti@...il.com>, linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: Proposal: Use hi-res clock for file timestamps On Wed, Aug 18, 2010 at 07:50:40PM +0200, Andi Kleen wrote: > > - nfsd updates it whenever it reads an mtime out of an inode that matches > > current_fs_time to the granularity of 1/HZ. > > That means you have a very very hot cache line on a larger system > if there are a lot of mtime changes. Probably a bad idea. Only if those mtime changes are also followed immediately by nfsd reads of the mtime. That will be the typical case for nfsd writes, though. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists