[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Re: A tale of three memory allocators
On Friday, March 18, 2005 8:56 am, Jesse Barnes wrote: > Rik van Riel <riel <at> redhat.com> writes: > > Two out of three is enough. I don't see the need for > > both CONFIG_DISCONTIGMEM and CONFIG_VIRTUAL_MEM_MAP. > > Well, we need it for sn2. We have very large memory holes within a node, > so we use the virtual memmap to make the mem_map array within a node > virtually contiguous. Of course I mean that the hypervisor probably has to support this stuff to work correctly on multi-node ia64 machines. The guests can probably get away with being special cased since they can be presented with a contiguous memory model (Dan is this what you're doing now?)... Thanks, Jesse ------------------------------------------------------- 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_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |