| 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, 24 Jan 2007 23:50:36 +1100 From: Nick Piggin <nickpiggin@...oo.com.au> To: Peter Zijlstra <a.p.zijlstra@...llo.nl> CC: Christoph Lameter <clameter@....com>, Aubrey Li <aubreylee@...il.com>, Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>, Robin Getz <rgetz@...ckfin.uclinux.org>, "Henn, erich, Michael" <Michael.Hennerich@...log.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [RFC] Limit the size of the pagecache Peter Zijlstra wrote: > On Tue, 2007-01-23 at 16:49 -0800, Christoph Lameter wrote: >>2. Insure rapid turnaround of pages in the cache. [...] > The only maybe valid point would be 2, and I'd like to see if we can't > solve that differently - a better use-once logic comes to mind. There must be something I'm missing with that point. The faster the turnaround of pagecache pages, the *less* efficiently the pagecache is working (assuming a rapid turnaround means a high rate of pages brought into, then reclaimed from pagecache). I can't argue that a smaller pagecache will be subject to a higher turnaround given the same workload, but I don't know why that would be a good thing. -- SUSE Labs, Novell Inc. Send instant messages to your online friends http://au.messenger.yahoo.com - 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