wxiwnd
520770da4c
Route supported multi-request CP shared-KV extend allocation through request-local owner plans so downstream direct-write paths can trust flattened out_cache_loc owner lanes. Unsupported page plans now fail fast instead of falling back to legacy allocation. Include the normative govctl RFC and completed work-item trail in the tracked repository; keep transient superpowers planning outside the sglang branch. Constraint: RFC-0001 W2 requires no legacy multi_batch fallback for supported bs>1 owner-lane allocation Rejected: concatenating requests before owner planning | CP ownership is request-relative Rejected: committing only docs/superpowers plan | it omits the normative RFC and work-item trail Confidence: high Scope-risk: moderate Directive: Preserve flattened request order when changing CP shared-KV allocation; run govctl from the sglang repository root Tested: remote uv test_nsa_cp_utils.py 39 OK; remote uv test_cp_shared_kv_layout.py 34 OK; remote uv test_alloc_pages_with_owners.py 10 OK; govctl check; git diff --check Not-tested: CUDA ETE/perf paths beyond focused W1/W2 unit suites
23 lines
1.1 KiB
TOML
23 lines
1.1 KiB
TOML
#:schema ../../../schema/clause.schema.json
|
|
|
|
[govctl]
|
|
id = "C-VERIFICATION"
|
|
title = "Verification requirements"
|
|
kind = "normative"
|
|
status = "active"
|
|
since = "0.1.0"
|
|
|
|
[content]
|
|
text = """
|
|
Tests MUST cover at least two requests with different prefix lengths and extend lengths.
|
|
|
|
Tests MUST verify that each newly allocated logical page in the output cache locations has the expected owner lane from the flattened owner list.
|
|
|
|
Tests MUST verify that owner-lane exhaustion for a batch-size greater than one case raises a recoverable capacity-wait error or returns an allocation failure to the caller that triggers that error path.
|
|
|
|
Tests MUST verify that batch-size one allocation remains compatible with the existing owner-lane behavior.
|
|
|
|
Tests SHOULD verify that supported batch-size greater than one CP shared-KV allocation does not call legacy allocation and does not emit a `multi_batch` fallback.
|
|
|
|
**Rationale:** These checks directly exercise the failure modes that W2 is intended to remove: cross-request owner mixing, wrong logical page owners, capacity fallback, and single-request regression."""
|