|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Xen 3.4.1 NUMA support
To: |
Jan Beulich <JBeulich@xxxxxxxxxx>, Andre Przywara <andre.przywara@xxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> |
Subject: |
RE: [Xen-devel] Xen 3.4.1 NUMA support |
From: |
Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx> |
Date: |
Tue, 10 Nov 2009 01:46:41 +0000 |
Accept-language: |
en-US |
Acceptlanguage: |
en-US |
Cc: |
George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, Papagiannis Anastasios <apapag@xxxxxxxxxxxx> |
Delivery-date: |
Mon, 09 Nov 2009 17:47:30 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<4AF84100020000780001E8CC@xxxxxxxxxxxxxxxxxx> |
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<bd4f4a54-5269-42d8-b16d-cbdfaeeba361@default> <4AF82F12.6040400@xxxxxxx> <4AF84100020000780001E8CC@xxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
AcphUKuGSqA8cb1oR3mD76TGYscOkQAVSiIQ |
Thread-topic: |
[Xen-devel] Xen 3.4.1 NUMA support |
> >>> Andre Przywara <andre.przywara@xxxxxxx> 09.11.09 16:02 >>>
> >BTW: Shouldn't we set finally numa=on as the default value?
>
> I'd say no, at least until the default confinement of a guest to a single
> node gets fixed to properly deal with guests having more vCPU-s than
> a node's worth of pCPU-s (i.e. I take it for granted that the benefits of
> not overcommitting CPUs outweigh the drawbacks of cross-node memory
> accesses at the very least for CPU-bound workloads).
What default confinement? I thought guests had an all-pCPUs affinity mask be
default?
I suspect we will get benefits enabling NUMA even if all the guests have
all-pCPUs affinity masks: all guests will have memory stripped across all
nodes, which is likely better than allocating from one node and then the other.
Obviously assigning VMs to node(s) and allocating memory accordingly is the
best plan.
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Xen 3.4.1 NUMA support, (continued)
- Re: [Xen-devel] Xen 3.4.1 NUMA support, George Dunlap
- RE: [Xen-devel] Xen 3.4.1 NUMA support, Ian Pratt
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Keir Fraser
- RE: [Xen-devel] Xen 3.4.1 NUMA support, Ian Pratt
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Jan Beulich
- RE: [Xen-devel] Xen 3.4.1 NUMA support,
Ian Pratt <=
- RE: [Xen-devel] Xen 3.4.1 NUMA support, Jan Beulich
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Keir Fraser
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Keir Fraser
- [Xen-devel] [PATCH] tools: avoid over-commitment if numa=on, Andre Przywara
|
|
|
|
|