[ovirt-devel] [Bug fix of NUMA feature] Add vNode run in pNode runtime information

Shi, Xiao-Lei (Bruce, HP Servers-PSC-CQ) xiao-lei.shi at hp.com
Thu May 22 02:13:03 UTC 2014


Hi all,

I'm working on the NUMA feature of oVirt.
The feature is already merged in oVirt 3.5.0 alpha 1. Currently, it only has the virtual numa node (vNode) pin to host numa node(pNode) information which is configured by user. We plan to collect the runtime information from vdsm that vNode run in which pNodes. Since this information is dynamic and changes more often, we want to let this information reported in the process of vm stats report.
According to the above requirement, we will do the following development in both engine and vdsm:
Vdsm side:

1.       In vm module, we will add a function to collect and calculate the real-time information that vNode run in pNodes. From caps module, we can get the cpu mapping information of each pNode; from vm conf, we can get the vcpu mapping information of each vNode; from libvirt api, we can get each vcpu run in which physical cpu runtime. According to the information, we can calculate the vNode run in pNodes information runtime.

2.       Add a key in vm stat map to hold the information and report it to engine.
Engine side:

1.       Currently we have the structure to store the vNode run in pNode information. In the structure, we have a field "ispinned" to represent if the vNode is configured by user to pin to the pNode, or it is runtime run in the pNode. Now we only need to parse the reported information from vdsm and update it in db.
We will open a bug to implement the requirement and merge it into 3.5.0.
Any comments and suggestions are welcome.

Thanks & Best Regards
Shi, Xiao-Lei (Bruce)

Hewlett-Packard Co., Ltd.
HP Servers Core Platform Software China
Telephone +86 23 65683093
Mobile +86 18696583447
Email xiao-lei.shi at hp.com<mailto:shiguo.li at hp.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20140522/f6c71258/attachment-0001.html>


More information about the Devel mailing list