| 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: <20100428055538.GA1730@ucw.cz> Date: Wed, 28 Apr 2010 07:55:39 +0200 From: Pavel Machek <pavel@....cz> To: Dan Magenheimer <dan.magenheimer@...cle.com> Cc: Avi Kivity <avi@...hat.com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org, jeremy@...p.org, hugh.dickins@...cali.co.uk, ngupta@...are.org, JBeulich@...ell.com, chris.mason@...cle.com, kurt.hackel@...cle.com, dave.mccracken@...cle.com, npiggin@...e.de, akpm@...ux-foundation.org, riel@...hat.com Subject: Re: Frontswap [PATCH 0/4] (was Transcendent Memory): overview Hi! > > Seems frontswap is like a reverse balloon, where the balloon is in > > hypervisor space instead of the guest space. > > That's a reasonable analogy. Frontswap serves nicely as an > emergency safety valve when a guest has given up (too) much of > its memory via ballooning but unexpectedly has an urgent need > that can't be serviced quickly enough by the balloon driver. wtf? So lets fix the ballooning driver instead? There's no reason it could not be as fast as frontswap, right? Actually I'd expect it to be faster -- it can deal with big chunks. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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