From: Jesse Barnes <jbarnes@engr.sgi.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: A tale of three memory allocators
Date: Fri, 18 Mar 2005 16:56:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20050318T175332-256@post.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.61.0503172345320.8711@chimarrao.boston.redhat.com
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
next prev parent reply other threads:[~2005-03-18 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 23:08 A tale of three memory allocators Magenheimer, Dan (HP Labs Fort Collins)
2005-03-18 4:48 ` Rik van Riel
2005-03-18 16:56 ` Jesse Barnes [this message]
2005-03-18 19:42 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 0:08 Ian Pratt
2005-03-18 19:44 Tian, Kevin
2005-03-18 19:48 Tian, Kevin
2005-03-18 20:07 Magenheimer, Dan (HP Labs Fort Collins)
2005-03-18 20:18 ` Andrew Theurer
2005-03-18 20:11 Magenheimer, Dan (HP Labs Fort Collins)
2005-03-18 20:24 ` Hollis Blanchard
2005-03-18 22:05 Tian, Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20050318T175332-256@post.gmane.org \
--to=jbarnes@engr.sgi.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.