| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [RFC] Xen NUMA strategy
|
To: |
Ian Pratt <Ian.Pratt@xxxxxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] [RFC] Xen NUMA strategy |
|
From: |
Aron Griffis <aron@xxxxxx> |
|
Date: |
Wed, 19 Sep 2007 23:09:38 -0400 |
|
Cc: |
Andre Przywara <andre.przywara@xxxxxxx>, "Xu, Anthony" <anthony.xu@xxxxxxxxx>, Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx |
|
Delivery-date: |
Wed, 19 Sep 2007 20:11:19 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<8A87A9A84C201449A0C56B728ACF491E260723@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
Mail-followup-to: |
Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, "Xu, Anthony" <anthony.xu@xxxxxxxxx>, Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, Andre Przywara <andre.przywara@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx |
|
References: |
<51CFAB8CB6883745AE7B93B3E084EBE2011113AE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <8A87A9A84C201449A0C56B728ACF491E260723@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.5.16 (2007-06-11) |
Ian Pratt wrote: [Tue Sep 18 2007, 04:43:24AM EDT]
> The way I see it, in most situations it will not make sense for guests
> to span NUMA nodes: you'll have a number of guests with relatively small
> numbers of vCPUs, and it probably makes sense to allow the guests to be
> pinned to nodes. What we have in Xen today works pretty well for this
> case, [snip]
One part that doesn't work well presently is memory locality. A guest
can be pinned to a CPU but its allocated memory might be on a distant
node...
Aron
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home