From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: [RFC] Replacing Xen's xmalloc engine and(?) API Date: Sat, 11 Oct 2008 15:59:18 -0700 (PDT) Message-ID: <2bfec152-d154-43d6-acae-b9abaf4f9a8f@default> References: <48F124C9.3040209@konink.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <48F124C9.3040209@konink.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan de Konink Cc: Diwaker Gupta , nitingupta910@gmail.com, "Xen-Devel (E-mail)" , kurt.hackel@oracle.com List-Id: xen-devel@lists.xenproject.org Yes. Well, for basic page de-duplication it probably is irrelevant, but for "advanced features" it will be more capable because it will handle near-page-size allocations much better. > -----Original Message----- > From: Stefan de Konink [mailto:stefan@konink.de] > Sent: Saturday, October 11, 2008 4:12 PM > To: Dan Magenheimer > Cc: Xen-Devel (E-mail); Diwaker Gupta; nitingupta910@gmail.com; Kurt > Hackel > Subject: Re: [Xen-devel] [RFC] Replacing Xen's xmalloc engine=20 > and(?) API >=20 >=20 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 > Dan Magenheimer schreef: > > Xen hypervisor experts -- >=20 > ... >=20 > > Comments? (on both the API proposal and the engine) >=20 > Is this engine capable of progressing to a memory=20 > de-duplication style? > Or is that outside the scope? >=20 >=20 > Stefan > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >=20 > iEYEAREKAAYFAkjxJMkACgkQYH1+F2Rqwn3H0wCfas1yNV+EXXwRuUVGZE5OpkKs > WVQAn0ViQ/B3HtXaZLj7vPM0CHKOXc8B > =3D2OZG > -----END PGP SIGNATURE----- >=20 >