|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: A tale of three memory allocators
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.
> I guess that having a NUMA aware allocator could come
> in handy though, so guest domains get their memory from
> the right node wrt. to where they get CPU time scheduled.
Yep, it would probably be a mistake to overoptimize Xen on NUMA at this point,
but doing basic things like this makes sense.
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
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] A tale of three memory allocators, Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-devel] A tale of three memory allocators, Ian Pratt
- RE: [Xen-devel] A tale of three memory allocators, Tian, Kevin
- RE: [Xen-devel] A tale of three memory allocators, Tian, Kevin
- RE: [Xen-devel] A tale of three memory allocators, Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-devel] A tale of three memory allocators, Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-devel] A tale of three memory allocators, Tian, Kevin
|
|
|
|
|