| 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
| ||
|
Message-ID: <4B38FC42.7000204@cs.helsinki.fi> Date: Mon, 28 Dec 2009 20:43:14 +0200 From: Pekka Enberg <penberg@...helsinki.fi> To: Andi Kleen <andi@...stfloor.org> CC: Nitin Gupta <ngupta@...are.org>, Hugh Dickins <hugh.dickins@...cali.co.uk>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 1/2] [mmotm] Add notifiers for various swap events Hi Andi, Andi Kleen wrote: >>> The first question to ask is if compressed swap is worth >>> it. Do you have benchmark numbers showing it to be an improvement? >>> Are there cases where it is slower than uncompressed swap? >>> >> http://code.google.com/p/compcache/wiki/Performance > > That should be included in the changelog of the patches. Which patches? The driver is already in staging and there's a pointer to the home page in linux/drivers/staging/ramzswap/ramzswap.txt >> ramzswap is an optional module. > > I have some doubts on the wisdom of making swap algorithms modular. > Better compile them in. Then you don't need messy notifiers either. What's so messy about them? The whole point of having the notifiers is to avoid CONFIG_RAMZSWAP in core kernel code... Pekka -- 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