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.

Sign up for GitHub

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

Jump to bottom

Support use_max_active_blocks_per_multiprocessor() on a config builder #580

Closed
eyalroz opened this issue Jan 29, 2024 · 1 comment
Closed

Support use_max_active_blocks_per_multiprocessor() on a config builder #580

eyalroz opened this issue Jan 29, 2024 · 1 comment
Assignees
@eyalroz
Labels
task

Comments

@eyalroz
Copy link
Owner

eyalroz commented Jan 29, 2024

For a kernel_t, we can obtain the maximum active blocks per SM; let's add a config builder method which uses this value to set the grid dims.
@eyalroz eyalroz added the task label Jan 29, 2024
@eyalroz eyalroz self-assigned this Jan 29, 2024
eyalroz added a commit that referenced this issue Jan 29, 2024
@eyalroz
Fixes #579, regards #580: Launch config builder additions
c6fb40a 
* Can now set the device on `launch_config_builder_t`, with either a device ID or a `device_t` reference
* Can now set the grid dimensions using the max number of blocks which may be active per multiprocessor (but note: that should be made lazy)
@eyalroz
Copy link
Owner Author

eyalroz commented Jan 29, 2024

Actually, we already have this with saturate_with_active_blocks().

@eyalroz eyalroz closed this as completed Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eyalroz eyalroz

Labels
task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eyalroz