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

Inconsistency with Barriers having workgroup sizes above 256 work items. #156

Open
CoreRasurae opened this issue Dec 16, 2019 · 2 comments
Labels
bug Fix something that is broken

Comments

@CoreRasurae
Copy link
Collaborator

For some reason, on some systems, the Barriers are not working properly. Inconsistent results are returned for workgroup sizes of 1024, or 512 on some NVIDIA systems, and 8192 workgroup sizes on some CPU systems.
The failing unit test is BarrierSupportTest.

@CoreRasurae
Copy link
Collaborator Author

NVIDIA NVS 4200M and NVIDIA GTX 760 pass the BarrierSupportTest on an Ubuntu 18.04 LTS, with nvidia-390, but a NVIDIA RTX 2070 is failing on a Ubuntu 16.04 LTS with Cuda 10-2, also GTX 1060 is failing on Arch linux.

@freemo freemo added the bug Fix something that is broken label Jan 29, 2020
@CoreRasurae
Copy link
Collaborator Author

In fact I've tested NVIDIA GT 1030 on the same system and the issue above is originated by the driver version. If using NVIDIA GT 1030 with nvidia-390 drivers the tests pass. If using the same NVIDIA GT 1030 on the same system, but with nvidia-440 drivers, the above test fails.

freemo pushed a commit that referenced this issue Jan 5, 2021
…eWorkGroupSize(), getKernelPreferredWorkGroupSizeMultiple(), getKernelMinimumPrivateMemSizeInUsePerWorkItem() and getKernelLocalMemSizeInUse() - Fixes refs #2, Fixes refs #156
freemo added a commit that referenced this issue Jan 5, 2021
Add support for getKernelMaxWorkGroupSize(), getKernelCompileWorkGroupSize(), gettKernelPreferredWorkGroupSizeMultiple(), getKernelMinimumPrivateMemSizeInUsePerWorkItem() and getKernelLocalMemSizeInUse() - Fixes refs #2, Fixes refs #156

See merge request aparapi/aparapi!20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fix something that is broken
Projects
None yet
Development

No branches or pull requests

2 participants