| 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: Fri, 14 Aug 2009 18:49:19 +0300 From: Al Boldi <a1426z@...ab.com> To: ngupta@...are.org Cc: Hugh Dickins <hugh.dickins@...cali.co.uk>, Matthew Wilcox <willy@...ux.intel.com>, Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: compcache as a pre-swap area Nitin Gupta wrote: > On 08/14/2009 09:32 AM, Al Boldi wrote: > > So once compcache fills up, it will start to age its contents into normal > > swap? > > This is desirable but not yet implemented. For now, if 'backing swap' is > used, compcache will forward incompressible pages to the backing swap > device. If compcache fills up, kernel will simply send further swap-outs to > swap device which comes next in priority. Ok, this sounds acceptable for now. The important thing now is to improve performance to a level comparable to a system with normal ssd-swap. Do you have such a comparisson? Another interresting benchmark would be to use compcache in a maximized configuration, ie. on a system w/ 1024KB Ram assign 960KB for compcache and leave 64KB for the system, and then see how it performs. This may easily pinpoint any bottlenecks compcache has, if any. Also, a link to the latest patch against .30 would be helpful. Thanks! -- Al -- 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