Re: [hwloc-users] Puzzled by the number of cores on i5-7500
I assume you need other people to answer as well, but here is what I get: $ sysctl -a | grep ^hw hw.ncpu: 4 hw.byteorder: 1234 hw.memsize: 8589934592 hw.activecpu: 4 hw.physicalcpu: 4 hw.physicalcpu_max: 4 hw.logicalcpu: 4 hw.logicalcpu_max: 4 hw.cputype: 7 hw.cpusubtype: 8 hw.cpu64bit_capable: 1 hw.cpufamily: 260141638 hw.cacheconfig: 4 1 1 4 0 0 0 0 0 0 hw.cachesize: 8589934592 32768 262144 6291456 0 0 0 0 0 0 hw.pagesize: 4096 hw.pagesize32: 4096 hw.busfrequency: 1 hw.busfrequency_min: 1 hw.busfrequency_max: 1 hw.cpufrequency: 34 hw.cpufrequency_min: 34 hw.cpufrequency_max: 34 hw.cachelinesize: 64 hw.l1icachesize: 32768 hw.l1dcachesize: 32768 hw.l2cachesize: 262144 hw.l3cachesize: 6291456 hw.tbfrequency: 10 hw.packages: 1 hw.optional.floatingpoint: 1 hw.optional.mmx: 1 hw.optional.sse: 1 hw.optional.sse2: 1 hw.optional.sse3: 1 hw.optional.supplementalsse3: 1 hw.optional.sse4_1: 1 hw.optional.sse4_2: 1 hw.optional.x86_64: 1 hw.optional.aes: 1 hw.optional.avx1_0: 1 hw.optional.rdrand: 1 hw.optional.f16c: 1 hw.optional.enfstrg: 1 hw.optional.fma: 1 hw.optional.avx2_0: 1 hw.optional.bmi1: 1 hw.optional.bmi2: 1 hw.optional.rtm: 1 hw.optional.hle: 1 hw.optional.adx: 1 hw.optional.mpx: 0 hw.optional.sgx: 0 hw.optional.avx512f: 0 hw.optional.avx512cd: 0 hw.optional.avx512dq: 0 hw.optional.avx512bw: 0 hw.optional.avx512vl: 0 hw.optional.avx512ifma: 0 hw.optional.avx512vbmi: 0 hw.targettype: Mac $ sysctl -a | grep ^machdep.cpu machdep.cpu.max_basic: 22 machdep.cpu.max_ext: 2147483656 machdep.cpu.vendor: GenuineIntel machdep.cpu.brand_string: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz machdep.cpu.family: 6 machdep.cpu.model: 158 machdep.cpu.extmodel: 9 machdep.cpu.extfamily: 0 machdep.cpu.stepping: 9 machdep.cpu.feature_bits: 9221960262849657855 machdep.cpu.leaf7_feature_bits: 43806655 machdep.cpu.extfeature_bits: 1241984796928 machdep.cpu.signature: 591593 machdep.cpu.brand: 0 machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C machdep.cpu.leaf7_features: SMEP ERMS RDWRFSGS TSC_THREAD_OFFSET BMI1 HLE AVX2 BMI2 INVPCID RTM SMAP RDSEED ADX IPT SGX FPU_CSDS MPX CLFSOPT machdep.cpu.extfeatures: SYSCALL XD 1GBPAGE EM64T LAHF LZCNT PREFETCHW RDTSCP TSCI machdep.cpu.logical_per_package: 16 machdep.cpu.cores_per_package: 8 machdep.cpu.microcode_version: 88 machdep.cpu.processor_flag: 1 machdep.cpu.mwait.linesize_min: 64 machdep.cpu.mwait.linesize_max: 64 machdep.cpu.mwait.extensions: 3 machdep.cpu.mwait.sub_Cstates: 1319200 machdep.cpu.thermal.sensor: 1 machdep.cpu.thermal.dynamic_acceleration: 1 machdep.cpu.thermal.invariant_APIC_timer: 1 machdep.cpu.thermal.thresholds: 2 machdep.cpu.thermal.ACNT_MCNT: 1 machdep.cpu.thermal.core_power_limits: 1 machdep.cpu.thermal.fine_grain_clock_mod: 1 machdep.cpu.thermal.package_thermal_intr: 1 machdep.cpu.thermal.hardware_feedback: 0 machdep.cpu.thermal.energy_policy: 1 machdep.cpu.xsave.extended_state: 31 832 1088 0 machdep.cpu.xsave.extended_state1: 15 832 256 0 machdep.cpu.arch_perf.version: 4 machdep.cpu.arch_perf.number: 8 machdep.cpu.arch_perf.width: 48 machdep.cpu.arch_perf.events_number: 7 machdep.cpu.arch_perf.events: 0 machdep.cpu.arch_perf.fixed_number: 3 machdep.cpu.arch_perf.fixed_width: 48 machdep.cpu.cache.linesize: 64 machdep.cpu.cache.L2_associativity: 4 machdep.cpu.cache.size: 256 machdep.cpu.tlb.inst.large: 8 machdep.cpu.tlb.data.small: 64 machdep.cpu.tlb.data.small_level1: 128 machdep.cpu.address_bits.physical: 39 machdep.cpu.address_bits.virtual: 48 machdep.cpu.core_count: 4 machdep.cpu.thread_count: 4 machdep.cpu.tsc_ccc.numerator: 284 machdep.cpu.tsc_ccc.denominator: 2 $ lstopo - Machine (8192MB total) + NUMANode L#0 (P#0 8192MB) + L3 L#0 (6144KB) Core L#0 L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + PU L#0 (P#0) L2 L#1 (256KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + PU L#1 (P#1) Core L#1 L2 L#2 (256KB) + L1d L#2 (32KB) + L1i L#2 (32KB) + PU L#2 (P#2) L2 L#3 (256KB) + L1d L#3 (32KB) + L1i L#3 (32KB) + PU L#3 (P#3) > Le 25 janv. 2018 à 19:18, Brice Goglin a écrit : > > lstopo - ___ hwloc-users mailing list hwloc-users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/hwloc-users
Re: [hwloc-users] Puzzled by the number of cores on i5-7500
It looks like our Mac OS X backend doesn't properly handle processors that support hyperthreading without actually having hyperthreads enabled in hardware. Your processor has 4-core without HT but it's based on a processor with up to 8 cores and 16 threads. Our current code uses the latter and therefore wrongly assume you have HT cores, hence reporting 2 HT cores instead of 4 noHT cores. I guess we would also be wrong if some cores or HT are disabled in software in Mac OS X. Anybody reading this from a Mac, could you send the output of these commands on your machine? sysctl -a | grep ^hw sysctl -a | grep ^machdep.cpu lstopo - Brice > > > Le 25/01/2018 à 07:14, Olivier Cessenat a écrit : >> Hello, >> >> I’m puzzled by the report from lstopo about the number of physical >> cores on an iMac with >> I5-7500. It is specified by Intel as a quad core processor and lstopo >> reports only 2 cores: >> lstopo >> << >> Machine (8192MB total) + NUMANode L#0 (P#0 8192MB) + L3 L#0 (6144KB) >> Core L#0 >> L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + PU L#0 (P#0) >> L2 L#1 (256KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + PU L#1 (P#1) >> Core L#1 >> L2 L#2 (256KB) + L1d L#2 (32KB) + L1i L#2 (32KB) + PU L#2 (P#2) >> L2 L#3 (256KB) + L1d L#3 (32KB) + L1i L#3 (32KB) + PU L#3 (P#3) >> >> >> When running system_profiler SPHardwareDataType >> I obtain: >> << >> Hardware: >> >> Hardware Overview: >> >> Model Name: iMac >> Model Identifier: iMac18,3 >> Processor Name: Intel Core i5 >> Processor Speed: 3,4 GHz >> Number of Processors: 1 >> Total Number of Cores: 4 >> L2 Cache (per Core): 256 KB >> L3 Cache: 6 MB >> Memory: 8 GB >> Boot ROM Version: IM183.0151.B00 >> SMC Version (system): 2.41f1 >> Serial Number (system): DGKV7HJCJ1GN >> Hardware UUID: 3FDAD77B-F4E8-50AB-B0FF-AA5C41CA35FA >> >> >> >> Is there a trick ? >> >> Thanks for you help, >> >> Olivier Cessenat >> >> >> >> ___ >> hwloc-users mailing list >> hwloc-users@lists.open-mpi.org >> https://lists.open-mpi.org/mailman/listinfo/hwloc-users > ___ hwloc-users mailing list hwloc-users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/hwloc-users
Re: [hwloc-users] hwloc-2.0rc1 failure on Solaris
Thanks, Brice. FYI, yes, 1.11.8 has no problem building with those flags. — Pavan Sent from my iPhone > On Jan 25, 2018, at 5:50 AM, Brice Goglin wrote: > > It is actually easy to fix, we just need to move hwloc's #include before > what base64.c actually #include's. That'll be fixed in rc2 too. > > Brice > > > >> Le 25/01/2018 à 10:56, Brice Goglin a écrit : >> Like the error below? >> >> This code hasn't changed recently. Did you ever build with these flags >> before? >> >> I am not sure I'll have time to fix yet another header crazyness before rc2. >> >> Brice >> >> >> >> CC base64.lo >> In file included from >> /builds/hwloc-master-20180124.2347.gitf53fe3a/include/private/private.h:29:0, >> from base64.c:128: >> /builds/hwloc-master-20180124.2347.gitf53fe3a/include/private/misc.h: In >> function 'hwloc_strncasecmp': >> /builds/hwloc-master-20180124.2347.gitf53fe3a/include/private/misc.h:370:10: >> error: implicit declaration of function 'strncasecmp'; did you mean >> 'strncmp'? [-Werror=implicit-function-declaration] >>return strncasecmp(s1, s2, n); >> ^~~ >> strncmp >> cc1: some warnings being treated as errors >> >> >>> Le 25/01/2018 à 10:45, Balaji, Pavan a écrit : >>> Hello, >>> >>> hwloc-2.0rc1 build seems to fail on Solaris, with the following CFLAGS: >>> >>> CFLAGS="-Werror-implicit-function-declaration -std=c99" >>> >>> I'm using gcc-4.8.2 >>> >>> Thanks, >>> >>> -- Pavan >>> >>> ___ >>> hwloc-users mailing list >>> hwloc-users@lists.open-mpi.org >>> https://lists.open-mpi.org/mailman/listinfo/hwloc-users > > ___ > hwloc-users mailing list > hwloc-users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/hwloc-users ___ hwloc-users mailing list hwloc-users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/hwloc-users
Re: [hwloc-users] hwloc-2.0rc1 failure on Solaris
It is actually easy to fix, we just need to move hwloc's #include before what base64.c actually #include's. That'll be fixed in rc2 too. Brice Le 25/01/2018 à 10:56, Brice Goglin a écrit : > Like the error below? > > This code hasn't changed recently. Did you ever build with these flags > before? > > I am not sure I'll have time to fix yet another header crazyness before rc2. > > Brice > > > > CC base64.lo > In file included from > /builds/hwloc-master-20180124.2347.gitf53fe3a/include/private/private.h:29:0, > from base64.c:128: > /builds/hwloc-master-20180124.2347.gitf53fe3a/include/private/misc.h: In > function 'hwloc_strncasecmp': > /builds/hwloc-master-20180124.2347.gitf53fe3a/include/private/misc.h:370:10: > error: implicit declaration of function 'strncasecmp'; did you mean > 'strncmp'? [-Werror=implicit-function-declaration] > return strncasecmp(s1, s2, n); > ^~~ > strncmp > cc1: some warnings being treated as errors > > > Le 25/01/2018 à 10:45, Balaji, Pavan a écrit : >> Hello, >> >> hwloc-2.0rc1 build seems to fail on Solaris, with the following CFLAGS: >> >> CFLAGS="-Werror-implicit-function-declaration -std=c99" >> >> I'm using gcc-4.8.2 >> >> Thanks, >> >> -- Pavan >> >> ___ >> hwloc-users mailing list >> hwloc-users@lists.open-mpi.org >> https://lists.open-mpi.org/mailman/listinfo/hwloc-users ___ hwloc-users mailing list hwloc-users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/hwloc-users
Re: [hwloc-users] hwloc-2.0rc1 failure on Solaris
Like the error below? This code hasn't changed recently. Did you ever build with these flags before? I am not sure I'll have time to fix yet another header crazyness before rc2. Brice CC base64.lo In file included from /builds/hwloc-master-20180124.2347.gitf53fe3a/include/private/private.h:29:0, from base64.c:128: /builds/hwloc-master-20180124.2347.gitf53fe3a/include/private/misc.h: In function 'hwloc_strncasecmp': /builds/hwloc-master-20180124.2347.gitf53fe3a/include/private/misc.h:370:10: error: implicit declaration of function 'strncasecmp'; did you mean 'strncmp'? [-Werror=implicit-function-declaration] return strncasecmp(s1, s2, n); ^~~ strncmp cc1: some warnings being treated as errors Le 25/01/2018 à 10:45, Balaji, Pavan a écrit : > Hello, > > hwloc-2.0rc1 build seems to fail on Solaris, with the following CFLAGS: > > CFLAGS="-Werror-implicit-function-declaration -std=c99" > > I'm using gcc-4.8.2 > > Thanks, > > -- Pavan > > ___ > hwloc-users mailing list > hwloc-users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/hwloc-users ___ hwloc-users mailing list hwloc-users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/hwloc-users
[hwloc-users] hwloc-2.0rc1 failure on Solaris
Hello, hwloc-2.0rc1 build seems to fail on Solaris, with the following CFLAGS: CFLAGS="-Werror-implicit-function-declaration -std=c99" I'm using gcc-4.8.2 Thanks, -- Pavan ___ hwloc-users mailing list hwloc-users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/hwloc-users
