Re: [libvirt] [PATCH v3 1/9] Implement public API for virDomainGetIOThreadsInfo

>> + unsigned char *cpumap; /* CPU map for thread */ >> + int cpumaplen; /* cpumap size */ > >> + size_t nresources; /* count of resources using IOThread */ >> + char **resources; /* array of resources using IOThread */ > > "resources" is too vague. Suggestion? Is "devices" better? Today it's the disk source path, but I remember reading something where an IOThread could be potentially used for something else (perhaps network, but I cannot find the reference quickly).