Re: [Libvir] Extending libvirt to probe NUMA topology

Daniel Veillard wrote: >which would return an XML instance as in virConnectGetCapabilities. I >toyed with the idea of extending virConnectGetCapabilities() to add a >topology section in case of NUMA support at the hypervisor level, but >it was looking to me that the two might be used at different times >and separating both might be a bit cleaner, but I could be convinced >otherwise. This doesn't change much the content in any way. >I think the most important in the call is to get the topology informations >as the number of processors, memory and NUMA cells are already available >from virNodeGetInfo(). I suggest a format exposing the hierarchy in the >XML structure, which will allow for more complex topologies for example >on Sun hardware: > >--------------------------------- ><topology> > > One small suggestion here... I've seen the term numanode used in some recent Xen patches. It would seem clearer to replace "cell(s)" with "numanode(s)". Then it is immediately evident what is being referred to, yet doesn't interfere with the libvirt term "node". > <cells num='2'>