[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v6 00/10] vnuma introduction
On Fri, Jul 18, 2014 at 7:48 AM, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
In the workaround I used I configured vcpus (as we have ht/smt turned on) caches as this: Â
Yep, thats what I see as well.Â
Running lstopo with vNUMA enabled in guest with 4 vnodes, 8 vcpus: root@heatpipe:~# lstopo Machine (7806MB) + L3 L#0 (7806MB 10MB) + L2 L#0 (7806MB 256KB) + L1d L#0 (7806MB 32KB) + L1i L#0 (7806MB 32KB) Â NUMANode L#0 (P#0 1933MB) + Socket L#0 Â Â Core L#0 + PU L#0 (P#0)
  Core L#1 + PU L#1 (P#4)  NUMANode L#1 (P#1 1967MB) + Socket L#1   Core L#2 + PU L#2 (P#1)   Core L#3 + PU L#3 (P#5)  NUMANode L#2 (P#2 1969MB) + Socket L#2   Core L#4 + PU L#4 (P#2)
  Core L#5 + PU L#5 (P#6)  NUMANode L#3 (P#3 1936MB) + Socket L#3   Core L#6 + PU L#6 (P#3)   Core L#7 + PU L#7 (P#7) Basically, L2 and L1 are shared between nodes :)
I have manipulated cache sharing options before in cpuid but I agree with Wei its just a part of the problem. Along with number of logical processor numbers (if HT is enabled), I guess we need to construct apic ids (if its not done yet, I could not find it) and
cache sharing cpuids maybe needed, taking into account pinning if set. Like its described here: "The Initial APIC ID is composed of the physical processor's ID and the logical processor's ID within the physical processor. The least significant bits of the APIC ID are used to identify the logical processors within a single physical processor." Â
-- Elena _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |