Repository navigation
Model L D3D12: runtime option l_color_early (default off): colour staging overlapped with the encoder block - #200
Merged
Merged
Conversation
… route's colour staging after the input encoder With l_color_early=on, on the direct-resource route with Model L's own post, l_direct_color (the post's colour staging: it reads only the game's colour texture and pi and writes color_net) runs right after the input encoder, and the launch after it goes without a UAV barrier (Device::unordered_next), so the staging overlaps the encoder block instead of running alone before the post. The post's barrier still orders its read of color_net, and that frame's late staging is skipped. The same kernel on the same inputs: the same bytes. Off (the default), nothing changes. The kernel line reports l_color_early=on. No kernel changes. Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
phantoslayer21
force-pushed
the
model-l/color-early
branch
from
November 14, 2026 21:18
7ae6627 to
e77d095
Compare
phantoslayer21
marked this pull request as ready for review
November 14, 2026 21:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #89
This adds a runtime option,
l_color_early, default off, for Model L on native D3D12 with the direct-resource route and its own post.With
l_color_early=on,l_direct_color(the post's colour staging) runs right after the input encoder instead of just before the post. The launch after it then goes without a UAV barrier (Device::unordered_next), so the staging overlaps the encoder block, which is issue-bound, while the staging is bandwidth-bound.l_direct_colorreads only the game's colour texture and pi and writes onlycolor_net. Neither is touched by the network. The post's own barrier still orders its read ofcolor_net, and that frame's late staging is skipped. So it's the same kernel on the same inputs.l_color_early=onwhen the option is set.This touches the own-post direct route, which is kern3's area. The change is kept to the launch position only; the kernel and the post are untouched.
Timing
Not measured here: no harness runs the direct-resource route. The release lead's next Cyberpunk payload run will time it on and off. The expected gain is up to the staging's own time (about 24 bytes per render pixel, bandwidth-bound).
Tested
test_l_runtime_frame.py: all 22 tests pass. The newtest_color_early_optionchecks that the option is parsed and reported, and that on the buffer route (no staging) the frames launch exactly what they launch without it.public_gates.pypasses. The LOOK lines carry no hit in this branch's files.Not tested