Repository navigation
Validate CPU engine contracts and coordinated 1-to-10 shard scaling - #13
Merged
Merged
Conversation
This was referenced Oct 20, 2026
loverustfs
marked this pull request as ready for review
October 21, 2026 00:51
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.
Change
Add a fake whole-block engine ABI harness, typed host DPU simulation messages, and a checked CPU/TCP-versus-host-simulation functional pair. Real engine and hardware execution remain explicitly unavailable.
Add an executable 1 → 3 → 10 shard scaling example with independent localhost TCP services and directories. It drains Get pins, stops/joins old owners, prepares epochs 1 → 2 → 3, publishes complete routes, rejects old local sessions and remote epochs, fences pending writes and demonstrates remapped misses followed by explicit recomputation. Fourteen per-shard roundtrips verify payload bytes and release. It is
SINGLE_PROCESS_LOCALHOST, not ten physical hosts or performance evidence.Document bootstrap, immutable limits, full route publication, remote-fence responsibility, restart/rollback and absent automatic migration. Add
scaling-smoketo the CPU regression runner and preserve all hardware/engine deferrals. This branch includes #10–#12 and the reply-budget regression fix.Validation
Run the retained CPU gate with a fresh evidence directory:
Fetch locked dependencies once before the offline run. The runner checks formatting, default/all-feature Clippy, workspace/doc tests, optional-feature refusal contracts and CPU demos; it writes results.json, environment.json, summary.md, JUnit and raw logs. GitHub CI runs Linux x86_64, native aarch64 and aarch64 qemu-user checks and uploads x86_64 regression evidence.
The final CPU profile contains 21 gates. The scaling example also runs under workspace all-target tests:
Boundaries
GCK1/GCKR and CacheIdentity remain unchanged. Missing, failed or unverified blocks require recomputation. No hot erasure coding, durability replicas, linked accelerator libraries or product performance samples are added. TCP remains a trusted-fabric plaintext transport; the bearer fingerprint does not provide mTLS.
Real RDMA/NIXL, GDS, BF3/DOCA/SPDK, vLLM export/import and live RustFS remain
NOT_RUN_HARDWARE. GPU/model execution remainsNOT_RUN_BUDGET; an approved model/license campaign remainsNOT_RUN_LICENSE.TCO_UNKNOWN,go_gate=NOT_EVALUATED, MooncakeNOT_LINKEDandNOT_A_PERFORMANCE_RESULTremain.Exact reviewed head
af5162912b87b24a722004aa61fece93b72fb7cf: all five required commands PASS, with 277 workspace tests, 93 rdma-nixl transport tests and 21/21 CPU gates. The checkout was clean before and after. Local evidence:artifacts/merge-final-required-commands/andartifacts/merge-final-cpu/. GitHub exact-head CI passes x86_64, native aarch64 and qemu-user; PR CI also passes all three.