Thanks, that worked well!
lstopo and the output of these commands are in agreement.
I consider this mystery (for me anyway) solved.
On Sat, Mar 5, 2016 at 8:57 AM, Samuel Holland wrote:
> On 03/04/2016 05:37 PM, Jeff wrote:
>
>> The output of lstopo shows that 0-6, 1-7, etc... are paired, which
On 03/04/2016 05:37 PM, Jeff wrote:
The output of lstopo shows that 0-6, 1-7, etc... are paired, which
is what I originally assumed (as a 4790k is 0-4, 1-5, with similar
architecture so I'd assume similar), but different from the virsh
capabilities output (which did not list siblings correctly fo
Oh awesome. I was not aware of "lstopo". Thanks! Interesting thing - for
me "virsh capabilities" and "lstopo" display same information. id,
core_id and siblings values seem to match. I mean id is always same as
core_id therefore siblings value makes sense. No idea why its different
on your cpu. Tec
The output of lstopo shows that 0-6, 1-7, etc... are paired, which is what
I originally assumed (as a 4790k is 0-4, 1-5, with similar architecture so
I'd assume similar), but different from the virsh capabilities output
(which did not list siblings correctly for me)
Pic: https://www.dropbox.com/s/m
Interesting, relevant results below:
32839588
The siblings value is equ
Run "virsh capabilities" and look for tag. It lists core
siblings. Its what you are looking for right? For me this script also is
little inconclusive, however seems like libvirt lists siblings right as
i cant pin one core to two physical cores that are not siblings.
On 2016.03.04 16:34, Jeff wrot
I'm trying to distinguish which cores are which on my Intel 5930k processor.
I ran the script at the console, with no other additional VM's, Docker, or
plugins running (I'm running UnRAID).
My output doesn't show any real differences between the cores, all 4's and
5's, with the expected 10 to itsel
