RE: [Xen-devel] A tale of three memory allocators

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

>-----Original Message-----
>From: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Ian Pratt
>Sent: Thursday, March 17, 2005 4:08 PM
>
>> Said patch is still pending because coincidentally Greg
>> is currently looking at porting Xen/ia64 to one of those newfangled
>> ia64 NUMA machines.  "I would like to turn on CONFIG_NUMA.
>> CONFIG_DISCONTIGMEM, and CONFIG_VIRTUAL_MEM_MAP," said Greg.
>
>I'd vote strongly for:
>Stick with Rusty's allocator and just have different instances for
>different memory banks. Wrap the allocation function to prioritise
which
>pool to allocate from. This handles discontig memory and NUMA nicely.
>
>
>Ian

I assume that we can have no change to Rusty's allocator at all, except
some wrap interfaces to buddy system, right? Slab should only focus on
memory in xenheap, while xenheap seems to be node irrespective... :)

Thanks,
Kevin


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel