Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chained CPU determination lookup #109

Open
PragTob opened this issue Jul 29, 2017 · 0 comments
Open

Chained CPU determination lookup #109

PragTob opened this issue Jul 29, 2017 · 0 comments

Comments

@PragTob
Copy link
Member

PragTob commented Jul 29, 2017

There's a lot of discussion of this topic in #108 . It's not a high priority now but I wanted to log the issue :) Oh yeah, this concerns Linux for now.

Basically, we got lots of different places where depending on the system we might get better or worse information (or none at all). Atm we use proc/cpuinfo but that might be hard to parse/architecture dependent. /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq is pretty cool but normal users don't always have access. lscpu might also work.

An idea would be that we perform a chained lookup like try sys/... first and see if we find good enough information, otherwise try another method and so on...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant