Chegu Vinod <chegu_vinod <at> hp.com> writes: > > Andrew Theurer <habanero <at> linux.vnet.ibm.com> writes: > > Regarding the -numa option : > > I had earlier (about a ~month ago) tried the -numa option. The layout I > specified didn't match the layout the guest saw. Haven't yet looked into the > exact reason...but came to know that there was already an open issue: > > https://bugzilla.redhat.com/show_bug.cgi?id=816804 > > Also remember noticing a warning message when the -numa option was used for a > guest with more than 64VCPUs. (in my case with 80 VCPUs). Will be looking at > the code soon to see if there is any limitation... > Just FYI... Made some minor changes in qemu to allow for >64 cpus while using the -numa option and was able to boot 80way guest with 8 numa nodes in them. With NUMA in the guest I got much better performance for AIM7-high-systime workload (pretty close to native!). Given the nature of this system intensive workload and a small memory footprint I didn't pin the VCPUs. Do expect to see a need for pinning the VCPUs while running memory intensive workloads. Still have to try out the experiments with the PV lock changes (instead of the current temporary workarounds). Thanks Vinod > > > > -Andrew Theurer > > > > -- > > To unsubscribe from this list: send the line "unsubscribe kvm" in > > the body of a message to majordomo <at> vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo <at> vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
