[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v6 02/23] xen: move NUMA_NO_NODE to public memory.h as XEN_NUMA_NO_NODE
On 02/03/15 17:43, Andrew Cooper wrote:
> On 02/03/15 17:34, David Vrabel wrote:
>>
>> A guest that previously had 2 vNUMA nodes is migrated to a host with
>> only 1 pNUMA node. It should still have 2 vNUMA nodes.
>
> A natural consequence of vNUMA is that the guest must expect the vNUMA
> layout to change across suspend/resume. The toolstack cannot guarentee
> that it can construct a similar vNUMA layout after a migration. This
> includes the toolstack indicating that it was unable to make any useful
> NUMA affinity with the memory ranges.
Eep! I very much doubt we can do anything in Linux except retain the
existing NUMA layout across a save/restore.
David
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
