@marcan this is a good heads-up, thanks for that. we had vaguely heard the pieces of it a long time ago but hadn't put together the practical significance.

@marcan
I am guilty of this. I'll have to go and check out that path in /sys.

@marcan then what was/is /proc/cpuinfo used for?

@marcan at least it doesn’t crash

@marcan yup, I do use at least 3 SDKs which do seem... of getting some wrong ideas from /proc/cpuinfo about the environment they are running in :|

@marcan ansible and puppet have had facter for ages to winkle out all of this sort of information in a standard YAML/JSON form ... facter is pretty standalone and works without the dependencies if needed - your example: facter --no-ruby -j processors

@marcan This is the most Mastodon post I ever read.

Thank you!

@marcan /me looks at gnome-control-center which tries to parse "model name" from /proc/cpuinfo for its system details view...

@marcan I'm actually writing a system info tool right now, and it *mostly* relies on /sys/devices/system/cpu for cross-architecture CPU properties. There are some properties in /proc/cpuinfo that can't be found in sysfs, but those are gated behind an architecture check at build time.

And as an addendum, it does properly report core and thread counts on ARM :)

@marcan CPU model unknown on aarch64 cause the aarch64 cpuinfo implementation does not print a string heh

@marcan Oh, never looked there, thanks!

@marcan Did you just assume my Unix-like OS? Your Unix clone has weird paths that my UNIX grandchild doeth not.
BYW both Neo- and screenfetch(1) are EOL. I recommend fastfetch(1) these days.
My English FOSS profile is @neb

@marcan /proc/cpuinfo is good for a quick view. ragnar@omnia:/sys/devices/system/cpu has to much i dont want or need

@marcan @geekbench

@marcan can you think of legitimate reasons for parsing cpuinfo/sysfs? The ones i've seen were hacks/workarounds.

@marcan does meminfo have a similar story or it is ok to parse?

@marcan interesting.

I’ll have to explore and expirament.

Thank you for sharing.

@marcan When all you need is quick grep through "cpu features" flags then `/proc/cpuinfo` gives you readable names.

`/sys/devices/system/cpu/modalias` gives you hex codes for which you need to have dictionary.

But yes - the rest of stuff is there and users should just use `lscpu` to get data.

@marcan and if all you need is to know how many threads to spawn to scale on cores:

sysconf(_SC_NPROCESSORS_CONF); /* processors configured */
sysconf(_SC_NPROCESSORS_ONLN); /* processors available */

is even more portable (though there are 2 different names depending on the OSes because why not).

@marcan Indeed, many years ago I added fallback implementations of the topology functions so that the information would be available on every architecture and config

@marcan@social.treehouse.systems no

@marcan FYI @serebit