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
CUDA: Fix test_pinned on Jetson #7190
Conversation
Pinning memory with `cuMemHostRegister()` now appears to be supported, but only for memory regions < 4MB. This commit fixes test_pinned by only attempting to pin a 2MB array on ARM.
Making this ready for review as it is a complete fix in itself, and I won't have time to look into whether I can reproduce the other (separate) issue. |
count = 262144 # 2MB | ||
else: | ||
count = 2097152 # 16MB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assumes an 8 byte intp
? Given a 4 byte intp
would lead to a smaller allocation size, I think this is still fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed. All systems that support CUDA are 64-bit anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the patch, changes look on on inspection. Need to run this on hardware to test.
BFID |
BF passed, but i thk we still need a Jetson test(?) |
That would be ideal, but it's up to you :-) |
I actually don't have a Xavier to make it work. Since I'm not seeing any new failures, i'm marking this as ready. |
Does this fail on a Jetson Nano? (I don't have one to test) |
CUDA: Fix test_pinned on Jetson
Pinning memory with
cuMemHostRegister()
now appears to be supported, but only for memory regions < 4MB. This commit fixes test_pinned by only attempting to pin a 2MB array on ARM.Marking as draft for now as there is another test case in Issue #2849 that is failing that I need to check.