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

Split have_a_single_lane_compute into a non-returning and returning variants #75

Open
eyalroz opened this issue May 16, 2020 · 0 comments
Assignees
Labels

Comments

@eyalroz
Copy link
Owner

eyalroz commented May 16, 2020

The have_a_single_lane_compute primitive currently returns a value. But - this value is only valid for the single computing lane, and the caller doesn't even know which lane that is. That renders returning the value useless.

We should therefore split this collaboration primitive into two variants:

  1. have_a_single_lane_execute() which returns void, and requires no warp-level synchronization; and
  2. have_a_single_lane_compute() which does return a value, but uses get_from_lane() to propagate the value to all lanes.
@eyalroz eyalroz added the Task label May 16, 2020
@eyalroz eyalroz self-assigned this May 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant