Open Stack

Hi,

In the current implementation scheme:
/nova/pci/stats.py
################################################################################
 def _filter_pools_for_numa_cells(pools, numa_cells):
        # Some systems don't report numa node info for pci devices, in
        # that case None is reported in pci_device.numa_node, by adding 
None
        # to numa_cells we allow assigning those devices to instances with
        # numa topology
        numa_cells = [None] + [cell.id for cell in numa_cells]
#################################################################################
If some compute nodes don't report numa node info for pci devices.
Then these pci devices will be regarded as "belong to all numa node" to 
deal with by default.
This can lead to a problem:
Pci devices is not on the numa node which CPU\MEM on.
In this way, the real purpose of I/O (PCIe) Based NUMA Scheduling is not 
reached.
More serious is that the user will be wrong thought pci devices is on the 
numa node that CPU\MEM on.
The truth is, there are still many systems don't report numa node info for 
pci devices.
So, i think this bug need fixed.

#link：
https://bugs.launchpad.net/nova/+bug/1551504
 
https://review.openstack.org/#/c/298179/

Best regards，

Jinquan Ni


Ni Jinquan  倪进权
NAIL, NIV Nanjing Dept.I



R&D Building, ZTE Plaza, #6 Huashen Ave. 
Yuhuatai District, Nanjing, P.R.China, 210012
T: +86 025-52877383    M: +86 13584094152
E: ni.jinquan at zte.com.cn
www.zte.com.cn

欢迎访问OpenCOS门户  http://opencos.zte.com.cn 

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160621/a7d103ff/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 6015 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160621/a7d103ff/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 2054 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160621/a7d103ff/attachment-0001.gif>