It seems that numad is libvirt specific - is that the case? I'm not sure if there is a daemon for other hypervisors but would it make sense to have this functionality in OpenStack so we can extend it to work for each hypervisor allowing it to control the affinity in their own way? I guess this would need the Pinhead tool to either support multiple hypervisors or provide the pinning strategy to Nova which could then invoke the individual drivers.
Outside numa optimisations I think there are good reasons for Nova to support modifying the affinity / pinning rules - for example I can imagine that some flavours might be permitted dedicated or isolated vCPUs? Integrating this tool would allow us to provide it further hints/rules defined by the flavour or administrator. Bob -----Original Message----- From: Russell Bryant [mailto:[email protected]] Sent: 20 June 2013 17:48 To: [email protected] Subject: Re: [openstack-dev] Efficiently pin running VMs to physical CPUs automatically On 06/20/2013 10:36 AM, Giorgio Franceschi wrote: > Hello, I created a blueprint for the implementation of: > > A tool for pinning automatically each running virtual CPU to a physical > one in the most efficient way, balancing load across sockets/cores and > maximizing cache sharing/minimizing cache misses. Ideally able to be run > on-demand, as a periodic job, or be triggered by events on the host (vm > spawn/destroy). > > Find it at https://blueprints.launchpad.net/nova/+spec/auto-cpu-pinning > > Any inputappreciated! I'm actually surprised to see a new tool for this kind of thing. Have you seen numad? -- Russell Bryant _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
