Repository navigation
Rename compute size limits for clarity - #1991
Conversation
| compute stage {{GPUShaderModule}} entry-point. | ||
|
|
||
| <tr><td><dfn>maxComputePerDimensionDispatchSize</dfn> | ||
| <tr><td><dfn>maxComputeDispatchDimension</dfn> |
There was a problem hiding this comment.
We didn't discuss this rename previously. I don't really love the name - "dimension" singular isn't nearly as clear as "dimensions" plural.
I wonder if there's any reason we should have separate x/y/z limits for dispatches like we have for workgroup sizes.
There was a problem hiding this comment.
maxDispatchSizePerDimension? That or maxDispatchGridSize seems fine.
There was a problem hiding this comment.
It seems to me that both could be confusing wrt whether they are about the numbers passed to dispatch, or the total number of invocations in each dimension.
Perhaps, it would be more explicit to say maxComputeWorkgroupCountPerDimension?
There was a problem hiding this comment.
My only reservation with that name is it no longer says "dispatch", which is the place where this validation takes place. But otherwise I like it; applied.
There was a problem hiding this comment.
s/maxComputeWorkgroupsPerDimension/maxDispatchWorkgroupsPerDimension/g ?
Fixes #1929
Preview | Diff