Hi,

The use cases fro CPU pinning are exactly like discussed above: (1)
lowering guest scheduling latencies and (2) improving networking latencies
by pinning the SR-IOV IRQ's to specific cores. There is also a third use
case, (3) avoiding long latencies with spinlocks.

> On Wed, Nov 13, 2013 at 8:20 PM, Jiang, Yunhong <yunhong.ji...@intel.com>
 wrote:

>
>> Similarly, once you start talking about doing SR-IOV networking I/O
>> passthrough into a guest (for SDN/NFV stuff) for optimum efficiency it
>> is beneficial to be able to steer interrupts on the physical host to the
>> specific cpus on which the guest will be running.  This implies some
>> form of pinning.

> Still, I think hypervisor should achieve this, instead of openstack.

How would this work? As a solution, this would be much better since then
OpenStack would have much less low-level work to do.

-Tapio
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to