-
Notifications
You must be signed in to change notification settings - Fork 320
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
Correspondence Reference: Limits #3088
Conversation
51167b6
to
81bb6bf
Compare
c37fc0f
to
494dcdd
Compare
Documents how to compute limits on each platform. Hopefully will be expanded with more API and shading language correspondence tables in the future. Subsumes Limits.md. Fixes gpuweb#3027
This comment was marked as outdated.
This comment was marked as outdated.
@cwfitzgerald you may also be interested in this |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
Good stuff. Do note that FF has had trouble with buffer sizes above 2GB: gfx-rs/wgpu#2796 |
Previews, as seen when this build job started (586d304): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for putting this together! Two minor style nits, though I don't consider either of them to be blocking.
<th>`maxStorageTexturesPerShaderStage` | ||
<td>[#409](https://github.com/gpuweb/gpuweb/issues/409) | ||
<td>`maxPerStageDescriptorStorageImages` | ||
<td rowspan=2>*Strategy-dependent.* Allocate `Maximum number of Unordered Access Views in all descriptor tables across all stages` across these two limits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An alternative would be to do these as footnotes, no rowspans, put "[1]"/"[2]"/"[3]" in each cell and then put the text at the bottom.
Previews, as seen when this build job started (565d628): |
The issues certainly read better now, thanks! Not sure how critical I think it is to change the rowspans, they're parse-able it just take a moment to line things up visually. Still LGTM. |
* Correspondence Reference: Limits Documents how to compute limits on each platform. Hopefully will be expanded with more API and shading language correspondence tables in the future. Subsumes Limits.md. Fixes gpuweb#3027 * update Vulkan maxColorAttachments * fix for d3d12 minStorageBufferOffsetAlignment * fix dark mode * add some missing links * td.issue -> td p.issue * 4GiB or 2GiB
For rendered version, see preview link below
Documents how to compute limits on each platform. Subsumes Limits.md.
Fixes #3027