From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan de Konink Subject: Re: [RFC] Replacing Xen's xmalloc engine and(?) API Date: Sun, 12 Oct 2008 00:12:25 +0200 Message-ID: <48F124C9.3040209@konink.de> References: <2ed5b44f-1700-4505-bad4-37c76c85e617@default> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2ed5b44f-1700-4505-bad4-37c76c85e617@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: Diwaker Gupta , nitingupta910@gmail.com, "Xen-Devel (E-mail)" , kurt.hackel@oracle.com List-Id: xen-devel@lists.xenproject.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dan Magenheimer schreef: > Xen hypervisor experts -- ... > Comments? (on both the API proposal and the engine) Is this engine capable of progressing to a memory de-duplication style? Or is that outside the scope? Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREKAAYFAkjxJMkACgkQYH1+F2Rqwn3H0wCfas1yNV+EXXwRuUVGZE5OpkKs WVQAn0ViQ/B3HtXaZLj7vPM0CHKOXc8B =2OZG -----END PGP SIGNATURE-----