linux-kernel - Re: compcache as a pre-swap area (was: [PATCH] swap: send callback when swap slot is freed)

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:	Thu, 13 Aug 2009 23:01:49 +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 (was: [PATCH] swap: send callback 
	when swap slot is freed)

On Thu, Aug 13, 2009 at 10:35 AM, Al Boldi<a1426z@...ab.com> wrote:
> Nitin Gupta wrote:
>> BTW, last time compcache was not accepted due to lack of performance
>> numbers. Now the project has lot more data for various cases:
>> http://code.google.com/p/compcache/wiki/Performance
>> Still need to collect data for worst-case behaviors and such...
>
> I checked the link, and it looks like you are positioning compcache as a swap
> replacement.  If so, then repositioning it as a compressed pre-swap area
> working together with normal swap-space, if available, may yield a much more
> powerful system.
>
>

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).

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/