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

Non-transpose gemv should use TeamPolicy on GPUs #926

Closed
brian-kelley opened this issue Apr 1, 2021 · 1 comment
Closed

Non-transpose gemv should use TeamPolicy on GPUs #926

brian-kelley opened this issue Apr 1, 2021 · 1 comment

Comments

@brian-kelley
Copy link
Contributor

brian-kelley commented Apr 1, 2021

Our implementation of dense mat-vec (gemv) uses a range policy (single level of parallelism) on all execution spaces. It should be using a TeamPolicy since it's trivial to parallelize the sums within each row.

@brian-kelley
Copy link
Contributor Author

This should be benchmarked for local matrices sized about 1e4 x 1e5, since this is getting used on large row-partitioned square matrices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants