Skip to content

Accept arbitrary HMA page boundaries with CUDA restore configuration - #29

Closed
FujitsuPolycom wants to merge 1 commit into
codex/sparkcache-cuda-restore-terminologyfrom
codex/cuda-config-page-boundary-integration
Closed

Accept arbitrary HMA page boundaries with CUDA restore configuration#29
FujitsuPolycom wants to merge 1 commit into
codex/sparkcache-cuda-restore-terminologyfrom
codex/cuda-config-page-boundary-integration

Conversation

@FujitsuPolycom

Copy link
Copy Markdown
Owner

Resulting behavior

Page-semantic HMA extensions accept an authenticated cache boundary inside a larger group page. The codec compares complete opaque pages and carries a changed boundary-intersecting page, plus every following page, as immutable replacement data. Earlier byte-identical pages remain shared with the verified base snapshot.

Generated configuration continues to use only the canonical spark_cache_cuda_restore and spark_cache_cuda_placement_* keys supplied by the parent branch.

Correctness

Restore authenticates the embedded base manifest, delta objects, layout, block counts, semantic token boundaries, and reconstructed result digest before SparkCache CUDA placement. Invalid metadata or bytes still produce a cache miss and recomputation.

The GPU-free D-16 regression exercises SparkContextCacheConnector with the real ManifestStore: it stores and restores a 7,168-token GLM-shaped base, publishes a 12,032-token page delta, verifies that the encoded page payload remains smaller than a full snapshot, and restores full-attention and recurrent state byte-for-byte.

Compatibility

Cache namespace impact: none. CacheIdentity values, digest salts, chunk geometry, and the sparkcache-hybrid-page-delta/v1 and sparkcache-page-delta-manifest/v1 wire schemas are unchanged.

Deployable SparkCache source SHA-256: bc7cae86732c869ee8b2205d48ac5be6f580ee8b77a3e4ffd4c69dcd4f1bfae5.

This draft is stacked on #26 at commit b95aa8ab0068dc66a6892a5c311d7e9dd4a9c55a.

Distinct fail-closed condition

The error selected page window contains vLLM's null block occurs while the connector selects physical HMA blocks, before snapshot or page-delta encoding. This change does not alter that fail-closed condition. A separate regression must capture the recurrent group table and its authoritative checkpoint slot before any fix chooses a non-null block; scanning for an arbitrary non-null entry would not prove state identity.

Validation

  • python -m pytest sparkcache -q — 747 passed, 7 skipped
  • python -m pytest deploy -q — 108 passed, 1 skipped
  • python -m ruff check . — passed
  • Deployment source-attestation tests — 2 passed

Page-semantic extensions accept authenticated chunk boundaries that fall inside a larger HMA page. The delta reuses only byte-identical page prefixes, so a changed boundary-intersecting page and every following page are immutable replacement data.

This preserves the longest verified publication base instead of falling back to a full snapshot. Restore continues to authenticate the embedded base graph and reconstructed result before placement; invalid geometry or bytes remain a cache miss and recomputation.

Canonical SparkCache CUDA restore and placement configuration remains the only generated configuration vocabulary. Deployable SparkCache source SHA-256: bc7cae86732c869ee8b2205d48ac5be6f580ee8b77a3e4ffd4c69dcd4f1bfae5.

Cache namespace impact: none. CacheIdentity values, digest salts, chunk geometry, and page-delta wire schemas are unchanged.

Validation: python -m pytest sparkcache -q (747 passed, 7 skipped); python -m pytest deploy -q (108 passed, 1 skipped); python -m ruff check .; source-attestation tests (2 passed).
@FujitsuPolycom

Copy link
Copy Markdown
Owner Author

The resulting behavior and evidence are consolidated in retained draft stack #39#42#44. Independent heat and SSD research remains in #36. Closing this superseded draft and deleting only its remote head branch.

@FujitsuPolycom
FujitsuPolycom deleted the codex/cuda-config-page-boundary-integration branch August 31, 2026 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant