Re: [Libvir] Re: Proposal : add 3 functions to Libvirt API, for virtual CPUs

> /** > * virDomainGetVcpus: > * @domain: pointer to domain object, or NULL for Domain0 > * @info: pointer to an array of virVcpuInfo structures > * @maxinfo: number of structures in info array > * > * Extract information about virtual CPUs of a domain, store it in info > array. > * > * Returns the number of info filled in case of success, -1 in case of > failure. > */ > int virDomainGetVcpus(virDomainPtr domain, virVcpuInfoPtr info, int > maxinfo) Hum ... now the problem with that API entry point is that we 'burn' the maximum 256 processors in the ABI, i.e. if we ever need to go past 256 client and servers need to be recompiled. Maybe this is not a real problem in practice but that's annoying. Is there existing APIs doing this kind of things (in POSIX for example), and what hard limit did they use ? Maybe int virDomainGetVcpusNr(virDomainPtr domain, int nr, virVcpuInfoPtr info, int maxCPU); Where the maxCPU is defined by the client as the number of real CPU it defined in its virVcpuInfoPtr and then an iteration over the virtual CPU defined in the domain is possible too. Of course if the domain uses many virtual CPUs this would become expensive but somehow I don't see that being the common use, I would rather guess the domains created use a few CPUs even if instantiated on a very large machine. This > with the following structure (in libvirt.h): > /** > * virVcpuInfo: structure for information about a virtual CPU in a domain. > */ > #define VIR_MAX_CPUS 256 Hum, there is already NUMA machines with more than 256 processors, it's annoying to define an API limit when you know it is already breakable.