Today's article has you counting processors, cores, or threads really...

[KGIII]

The title says it well enough, though the article has some forced brevity...

https://linux-tips.us/a-few-ways-to-count-cpu-processors-or-cores/

Sure, feedback is awesome, though my connectivity kinda sucks for the past couple of days and is even worse today.

 

[f33dm3bits]

Isn't it juse easier to search how many cores your cpu has?

grep cores /proc/cpuinfo| head -n1
cpu cores    : 8

 

[KGIII]

There are all sorts of ways to get this info. Might as well as pick one and run with it.

 

[KGIII]

By the way, the article invites you to leave your method as a comment. ;-)

 

[Brickwizard]

By the way, the article invites you to leave your method as a comment.

I have....
inxi -c

 

[KGIII]

I have....
inxi -c

Yup, there's another one. There's also lscpu | grep "per socket" which should give an accurate result.

There's a ton of ways to get this data. The article contains only a few.

 

[dos2unix]

lshw -c cpu | grep config
configuration: cores=12 enabledcores=12 threads=24

cpuinfo | grep Count
Count: 24

lscpu | grep Core
Model name: AMD Ryzen 9 3900X 12-Core Processor
BIOS Model name: AMD Ryzen 9 3900X 12-Core Processor Unknown CPU @ 3.8GHz
Core(s) per socket: 12

 

[KGIII]

Y'all can free to add it to the article as a comment. ;-)

I'm now kinda curious as to how many possible ways you can get this information - probably excluding any GUI ways... If we include graphical applications, it's a bunch.

 

[f33dm3bits]

By the way, the article invites you to leave your method as a comment. ;-)

I just replied with a comment but my code tags don't work, and when I login to the backend it won't allow me to edit my comment.

 

[KGIII]

Hmm... I don't think you have the rights to edit comments. Code tags are <code></code> over there. I'll take a peek at it in a moment. I'm just now really getting here for the day.

 

[KGIII]

You now have 15 minutes to edit comments after submitting them. It's a fairly obvious feature, appearing after you submit your comment.