|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] RE: Host Numa informtion in dom0
To: |
Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, "Kamble, Nitin A" <nitin.a.kamble@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Andre Przywara <andre.przywara@xxxxxxx> |
Subject: |
RE: [Xen-devel] RE: Host Numa informtion in dom0 |
From: |
"Nakajima, Jun" <jun.nakajima@xxxxxxxxx> |
Date: |
Tue, 9 Feb 2010 14:03:19 -0800 |
Accept-language: |
en-US |
Acceptlanguage: |
en-US |
Cc: |
|
Delivery-date: |
Tue, 09 Feb 2010 14:03:46 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<06d2c17f-cf69-4ef6-ab29-163bb3038bdb@default> |
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: |
<8EA2C2C4116BF44AB370468FBF85A7770123904A29@xxxxxxxxxxxxxxxxxxxxxxxxxxxx 4FA716B1526C7C4DB0375C6DADBC4EA342D83D9EBC@xxxxxxxxxxxxxxxxxxxxxxxxx> <06d2c17f-cf69-4ef6-ab29-163bb3038bdb@default> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
Acqmop5L3QsVe8CfR0aHas7eOE0mgwChKVxw |
Thread-topic: |
[Xen-devel] RE: Host Numa informtion in dom0 |
Dan Magenheimer wrote on Fri, 5 Feb 2010 at 12:33:19:
> It would be good if the discussion includes how guest NUMA
> works with (or is exclusive of) migration/save/restore. Also,
> the discussion should include the interaction (or exclusivity
> from) the various Xen RAM utilization technologies -- tmem,
> page sharing/swapping, and PoD. Obviously it would be great
> if Xen could provide both optimal affinity/performance and optimal
> flexibility and resource utilization, but I suspect that will
> be a VERY difficult combination.
>
I think migration/save/restore should be excluded at this point, to keep the
design/implementation simple; it's a performance/scalability feature.
Jun
___
Intel Open Source Technology Center
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|