[libvirt] Add hyperthreaded sibling info to virsh capabilities
dustymabe at gmail.com
Wed Nov 7 18:24:28 UTC 2012
On Tue, Oct 30, 2012 at 7:32 PM, Eric Blake <eblake at redhat.com> wrote:
> On 10/29/2012 11:57 AM, Dusty Mabe wrote:
> > Thoughts?
> Sounds like a worthwhile idea; I'm looking forward to seeing what
> patches you come up with.
I have added thread_siblings, core_siblings, and total memory
information to the virsh capabilities output for a NUMA Cell. In my
opinion the most important of these are the thread_siblings and memory
information, but since it was easy to add, I also included the
The problem with this is that some topologies will most likely have
redundant information (see core_siblings below) :
<cpu id='0' thread_siblings='0,12'
<cpu id='2' thread_siblings='2,14'
<cpu id='4' thread_siblings='4,16'
<cpu id='6' thread_siblings='6,18'
As I don't exactly have a need for the core_siblings information right
now I will probably just revert it to just have the memory and
thread_sibling information unless others think i should leave it in.
More information about the libvir-list