-
Notifications
You must be signed in to change notification settings - Fork 15
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
Failed to add core affinity to core 64 on linux but not on windows #38
Comments
Can you show the entire error? |
That was the entire error/warning. To reproduce it, press 1 to do stress test, then press enter to run. Everything will run as usual, except that when allocating memory it will display that warning in red. Both the static and dynamic versions show the same warning. No such warning in windows. If you like a screenshot I can get it to you tomorrow. |
So I cannot reproduce this myself because my biggest system only has 16 cores. So I can only debug this through whatever information you can provide. |
Can you also post the full contents of |
The output is very long. So I am pasting only the output for core #1 and #64 processor : 0 processor : 64 |
Can you zip the entire file and attach it? I need to see all of it to see if it's skipping any IDs. Also, can you post a screenshot of the exact error(s)? |
Nevermind, I think I found an issue that could cause this. Fix will be rolled out in v0.8.3. Thanks for reporting this! |
Thanks! Can you shed a bit light on this? It is a bug or something wrong with my end that I need to look into? |
Off-by-one error in the CPU mask allocation: Wrong Code: Correct Code: When called with (core_id = 64), the old code only allocates enough mask bits for 64 cores (0-63). Assuming the underlying representation is an array of 64-bit integers, core 64 would spill to the next integer - which never got allocated. So I expect every core ID that's a multiple of 64 to potentially fail. Nothing you can do it about it on your side. |
I see. Just to make sure, there are 96 logical cores in this CPU. There is no warning for core 65, 66, ..., 95. Only core 64 had a warning. |
Only core #'s that are divisible by 64 will under allocate from this off-by-one error. |
Got it. Makes sense. Thanks for the fix. |
See if latest fixed this: https://github.com/Mysticial/y-cruncher/releases/tag/v0.8.3.9531 |
When I run y-cruncher component stress test on Ubuntu it issues an warning in red: failed to add core affinity to core 64. However there is no error if I run the same stress test on windows.
Ubuntu 22.04
Y-cruncher 0.8.2
Epyc 9004 processor
The text was updated successfully, but these errors were encountered: