Skip to content

chore[gpu]: split plan into unmaterialized / materialized#7175

Merged
0ax1 merged 1 commit intodevelopfrom
ad/check-max-shared-memory
Mar 26, 2026
Merged

chore[gpu]: split plan into unmaterialized / materialized#7175
0ax1 merged 1 commit intodevelopfrom
ad/check-max-shared-memory

Conversation

@0ax1
Copy link
Copy Markdown
Contributor

@0ax1 0ax1 commented Mar 26, 2026

This allows for checking whether the shared memory usage blows past the max GPU device shared memory before launching the dyn dispatch kernel, as well as having a separate materialize step we can fine tune that moves buffers from the host to the GPU.

@0ax1 0ax1 changed the title refactor: split dispatch plan into unmaterialized and materialized chore: split dispatch plan into unmaterialized / materialized Mar 26, 2026
@0ax1 0ax1 added the changelog/chore A trivial change label Mar 26, 2026
@0ax1
Copy link
Copy Markdown
Contributor Author

0ax1 commented Mar 26, 2026

I'll rework how we properly account for and allocate shared memory for the GPU in a follow up.

@0ax1 0ax1 changed the title chore: split dispatch plan into unmaterialized / materialized chore[cuda]: split dispatch plan into unmaterialized / materialized Mar 26, 2026
@0ax1 0ax1 changed the title chore[cuda]: split dispatch plan into unmaterialized / materialized chore[gpu]: split dispatch plan into unmaterialized / materialized Mar 26, 2026
@0ax1 0ax1 changed the title chore[gpu]: split dispatch plan into unmaterialized / materialized chore[gpu]: split plan into unmaterialized / materialized Mar 26, 2026
@0ax1 0ax1 force-pushed the ad/check-max-shared-memory branch from b8093fe to aa85065 Compare March 26, 2026 13:04
@0ax1 0ax1 requested review from a10y and robert3005 March 26, 2026 13:06
…dPlan

This allows for checking whether the shared memory usage blows past
the max before launching the dyn dispatch kernel, and having a separate
materialize step we can fine tune that moves buffers to GPU from the host.

Signed-off-by: Alexander Droste <alexander.droste@protonmail.com>
@0ax1 0ax1 force-pushed the ad/check-max-shared-memory branch from aa85065 to f1d4355 Compare March 26, 2026 15:51
@0ax1 0ax1 enabled auto-merge (squash) March 26, 2026 18:39
@0ax1
Copy link
Copy Markdown
Contributor Author

0ax1 commented Mar 26, 2026

Note the state of this PR is kinda transient and will be reworked as part of: 2cb615e

@0ax1 0ax1 merged commit 7aa556a into develop Mar 26, 2026
64 checks passed
@0ax1 0ax1 deleted the ad/check-max-shared-memory branch March 26, 2026 18:41
@0ax1
Copy link
Copy Markdown
Contributor Author

0ax1 commented Mar 26, 2026

@a10y ❤️

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

Labels

changelog/chore A trivial change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants