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

Fails to detect lack of NUMA #1162

Closed
jpg0 opened this issue Oct 25, 2024 · 3 comments
Closed

Fails to detect lack of NUMA #1162

jpg0 opened this issue Oct 25, 2024 · 3 comments
Labels
bug This issue is a bug. closed-for-staleness

Comments

@jpg0
Copy link

jpg0 commented Oct 25, 2024

Describe the bug

System info tests fail on my machine due to attempt at using NUMA and finding an empty cpu group.

Expected Behavior

Tests pass, NUMA is detected as unavailable.

Current Behavior

common.c correctly loads libnuma, even references g_numa_available_ptr, however never actually checks to see it NUMA is available (it is not on my system, and returns -1). During the system info tests a single group is detected, however all cpus are in group -1 as returned by libnuma. This fails the test. Instead numa should be entirely disabled if it's unavailable.

Reproduction Steps

compile and run tests.

Possible Solution

Numa should be entirely disabled if it's unavailable. Note that if I remove libnuma.so.1, the tests pass as numa is correctly disabled.

Additional Information/Context

This is running on an Odroid N2+, using Ubuntu 22.04.

Amlogic S922X Processor
Quad-core Cortex-A73 and Dual-core Cortex-A53

aws-c-common version used

HEAD

Compiler and version used

gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)

Operating System and version

Ubuntu 22.04 aarch64

@jpg0 jpg0 added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Oct 25, 2024
@TingDaoK
Copy link
Contributor

Hi, thanks for reporting the issue. I put up a potential fix for the issue you mentioned.

However, unfortunately, we don't have the platform to test it out. Is it possible for you to test the branch here and let us know if it fixes your issue or not?

@jpg0
Copy link
Author

jpg0 commented Oct 29, 2024

Just tested and it all works now, so this branch is good. Thanks!

@TingDaoK
Copy link
Contributor

Thanks for confirming. The PR with the fix has been merged. Let us know if you have any further question!

@TingDaoK TingDaoK added the closing-soon This issue will automatically close in 5 days unless further comments are made. label Oct 29, 2024
@jmklix jmklix removed the needs-triage This issue or PR still needs to be triaged. label Oct 29, 2024
@github-actions github-actions bot added closed-for-staleness and removed closing-soon This issue will automatically close in 5 days unless further comments are made. labels Nov 2, 2024
@github-actions github-actions bot closed this as completed Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. closed-for-staleness
Projects
None yet
Development

No branches or pull requests

3 participants