Repository navigation
Conversation
… KiB stalls on AMD #1133 measured libc's forward rep movsb stalling on the AMD bench (Zen 2) when the destination sits 1-31 bytes above the source modulo 4 KiB: 3x at 256 B, 22x at 8 KiB, 3.5x at 1 MiB. 56305 rev. 3.02 §2.12 explains why: it judges store-to-load forwarding by address bits 11:0. Its route through a descending loop fixed the stall. Round 12, whose outcome was binding, closed #1133 instead: every routed build, with or without the AVX loop, ran never-routed 256 KiB copies about 7% slower in 5 of 5 paired boots. A base whose memcpy was merely moved did not, so the cost is in the routed code and its mechanism is unknown. This records the stall, the cost and an exit for a future approach. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Problem
#1133 measured a real stall in userland's
memcpyon the AMD bench (Zen 2). It is closed, because round 12's binding outcome rejected every routed build. The stall it measured, and the cost that sank its fix, need a record so they don't vanish with the PR.Change
Record-only: adds
issues/a-userland-forward-copy-a-short-way-above-its-source-modulo-4-kib-stalls-on-amd.md(kind: finding). It holds:memcpy;Checks
cargo test --lib -- sourcegate::tests::no_tracked_file_identifies_a_machine_or_its_networkwith the file tracked: exit 0.ToyOSOrg/evidencebranchpr-1133.🤖 Generated with Claude Code