Closed m-j-w closed 7 years ago
This actually seems to be a non-issue. /proc/cpuinfo
reports same L3 cache size:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz
stepping : 3
microcode : 0x19
cpu MHz : 3498.574
cache size : 6144 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl pni ssse3 lahf_lm
bogomips : 6997.14
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz
stepping : 3
microcode : 0x19
cpu MHz : 3498.574
cache size : 6144 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl pni ssse3 lahf_lm
bogomips : 6997.14
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
Per the log of pkglisting, the cache sizes are wrong. Should be 8MB L3, and L2 looks suspicious. It should also have AVX2. First Haswell Xeon tested on thus far. Also possible that its a hypervisor problem. Check after next tag: remember to add full dump of cpuid registers to tests, plus a dump of /proc/cpuinfo on linux.