Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
procinfo can't distinguish between cores and processors, as far as I know.
No, it can't. It will treat all cores as processors.
But for most desktop (home-usage) machines, the answer is 1
As far as I know only XEON motherboards, mostly used for servers, have multiple (up to 4) CPU sockets. But, of course, it might be that by now even Core * cpu's have real multi-processor capabilities. But a "normal" Core i? (or such) motherboard only has a single cpu socket, so only a single cpu (and only a single memory controller). It can have multiple cores, of course, but a core is NOT a full separate processor (among that because of the single memory processor, so all cores have to wait on each other to get/store data from/to RAM (or even L2 cache).
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 39 bits physical, 48 bits virtual
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
So this probably is a single cpu chip, with 2 cores and 2 threads per core, because I think the "Socket(s)" one gives the real number of physical cpu chips.
At least my system gives
Code:
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 23
Stepping: 10
CPU MHz: 3066.803
BogoMIPS: 6133.12
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 3072K
and I know it is a Core 2 Duo cpu, so a single chip with 2 cores.
Another way is
Code:
$ cat /proc/cpuinfo
(only giving the last core)
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E7600 @ 3.06GHz
stepping : 10
cpu MHz : 3066.803
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
bogomips : 6133.12
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
which gives the model name of the cpu chip too.
The OP hasn't told us yet if he wants to know the real physical number of cpu's or "how many parallel instruction streams can be processed", which will include cores and thread per core too.
I think you all are being very helpful with the OPs homework in both of their threads.
These threads will definitely help others in the future.
I for one, was pleased to learn about lscpu -- I've always just looked at Webmin's System Information page, but, of course, that requires installing and configuring Webmin
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.