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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 14 Aug 2009 10:23:56 +0530
From:	Nitin Gupta <ngupta@...are.org>
To:	Al Boldi <a1426z@...ab.com>
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

On 08/14/2009 09:32 AM, Al Boldi wrote:
> Nitin Gupta wrote:
>> compcache is really not really a swap replacement. Its just another
>> swap device that
>> compresses data and stores it in memory itself. You can have disk
>> based swaps along
>> with ramzswap (name of block device).
>
> 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.

Nitin
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ