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

TaskPolicy<Cuda> performance requires teams mapped to warps #218

Closed
hcedwar opened this issue Mar 17, 2016 · 0 comments
Closed

TaskPolicy<Cuda> performance requires teams mapped to warps #218

hcedwar opened this issue Mar 17, 2016 · 0 comments
Assignees
Labels
Enhancement Improve existing capability; will potentially require voting
Milestone

Comments

@hcedwar
Copy link
Contributor

hcedwar commented Mar 17, 2016

The sparse cholesky example using TaskPolicy has 12% occupancy.
Probable fix is to support mapping of thread teams onto warps where the block size is multiple warps.
This requires enhancement of the thread team's team-level collectives and nested parallel operations.
A possible redesign is to replace the team-size integer parameter with a "large/small" value that allows the TeamPolicy and TaskPolicy to choose a device-appropriate value for large and small.

@hcedwar hcedwar added the Enhancement Improve existing capability; will potentially require voting label Mar 17, 2016
@hcedwar hcedwar added this to the Spring 2016 milestone Mar 17, 2016
@hcedwar hcedwar self-assigned this Mar 17, 2016
@hcedwar hcedwar modified the milestones: Summer 2016, Spring 2016 Apr 27, 2016
@crtrott crtrott closed this as completed Sep 3, 2016
@hcedwar hcedwar added this to Backlog in On-node Task DAG Apr 19, 2017
@hcedwar hcedwar moved this from Feature Backlog to Done in On-node Task DAG Apr 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improve existing capability; will potentially require voting
Projects
No open projects
Development

No branches or pull requests

2 participants