-
Notifications
You must be signed in to change notification settings - Fork 55
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
ppc64_cpu failed on system with 1280 cores #34
Comments
cat /etc/os-releaseNAME="Red Hat Enterprise Linux" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8" ppc64_cpu --cores-presentNumber of cores present = 160 ppc64_cpu --smtSMT=8 |
Looks like ppc64_cpu needs changes for this to work on systems with 1024+ CPUs:
From sched_setaffinity's man page:
|
The command "ppc64_cpu --frequency" failed on a Power system with 1280 threads as below:
ppc64_cpu --frequency
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
sched_setaffinity: Invalid argument
The text was updated successfully, but these errors were encountered: