From: Ryan Harper <ryanh@us.ibm.com>
To: David Pilger <pilger.david@gmail.com>
Cc: xen-devel@lists.xensource.com, ryanh@us.ibm.com
Subject: Re: NUMA and SMP
Date: Sun, 14 Jan 2007 13:00:46 -0600 [thread overview]
Message-ID: <20070114190046.GA16970@us.ibm.com> (raw)
In-Reply-To: <280848580701140355l7ed6a198l21aa3b36fc8bddbd@mail.gmail.com>
* David Pilger <pilger.david@gmail.com> [2007-01-14 06:04]:
> Hi all,
>
> 1. Does desktop computers, such as intel dual core really benefit from NUMA?
Desktop computers with AMD chips which include a memory bus on the cpu
have NUMA characteristics that can benefit from keeping memory close to
the cpu.
> 2. Does it have a real effect on the performance of Xen?
I've [1]posted previously to the list on the performance benefit for NUMA
systems and that there is no regression for non-NUMA systems.
> 3. Can't we let the guest OS manage NUMA instead of Xen? what is the
> difference? and why is it implemented in Xen?
Xen owns all of the system memory and also controls the allocation of
that memory and therefor determines what memory and which processors are
in use for a guest. If we are to be able to create a guest with memory
close to the physical processors in-use, then we must understand the
topology of the system when we allocate memory for the guest.
I'm not sure I understand entirely what you mean by letting the guest OS
manage NUMA instead. However, the current Xen NUMA implementation does
not export the domain's NUMA-ness to the guest kernel, but that is the
next logical step. Not only allocate memory to the guest in a
NUMA-aware fashion, but in the case that we are required to give memory
to a guest from multiple NUMA nodes, to export the guest topology such
that if the guest OS is NUMA-aware, it can make NUMA-aware decisions.
1. http://lists.xensource.com/archives/html/xen-devel/2006-09/msg00958.html
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2007-01-14 19:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 11:55 NUMA and SMP David Pilger
2007-01-14 19:00 ` Ryan Harper [this message]
2007-01-15 17:21 ` Anthony Liguori
2007-01-16 10:47 ` Petersson, Mats
2007-01-16 13:55 ` Emmanuel Ackaouy
2007-01-16 14:19 ` Petersson, Mats
2007-01-16 16:13 ` Emmanuel Ackaouy
2007-01-16 16:30 ` Petersson, Mats
2007-03-20 13:10 ` tgh
2007-03-20 13:19 ` Petersson, Mats
2007-03-20 13:49 ` tgh
2007-03-20 15:50 ` Petersson, Mats
2007-03-20 16:45 ` Ryan Harper
2007-03-20 16:47 ` Petersson, Mats
2007-03-20 13:51 ` Daniel Stodden
2007-03-21 1:08 ` tgh
2007-03-21 2:45 ` Daniel Stodden
2007-03-22 1:16 ` tgh
2007-03-22 10:42 ` Daniel Stodden
2007-03-22 12:13 ` tgh
2007-03-22 12:28 ` Daniel Stodden
2007-03-22 13:02 ` Ryan Harper
2007-03-22 14:56 ` Daniel Stodden
2007-03-22 15:12 ` Ryan Harper
2007-03-22 15:38 ` Daniel Stodden
2007-03-22 16:01 ` Ryan Harper
2007-03-22 16:22 ` Daniel Stodden
2007-03-22 17:02 ` Ryan Harper
2007-03-23 5:47 ` tgh
2007-03-23 14:42 ` Ryan Harper
2007-03-23 14:48 ` Petersson, Mats
2007-03-28 1:50 ` tgh
2007-03-28 2:01 ` Ryan Harper
2007-03-28 21:25 ` The context switch overhead comparison between vmexit/vmentry and hypercall Liang Yang
2007-01-16 14:51 ` Re: NUMA and SMP ron minnich
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=20070114190046.GA16970@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=pilger.david@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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.