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
21 lines
1.0 KiB
TOML
21 lines
1.0 KiB
TOML
#:schema ../../../schema/clause.schema.json
|
|
|
|
[govctl]
|
|
id = "C-CAPACITY-AND-EVICTION"
|
|
title = "Owner-lane capacity and eviction"
|
|
kind = "normative"
|
|
status = "active"
|
|
since = "0.1.0"
|
|
|
|
[content]
|
|
text = """
|
|
If owner-lane allocation cannot be satisfied from immediately available owner-lane pages, the system SHOULD use the existing owner-lane eviction and retry mechanism before reporting capacity failure.
|
|
|
|
After owner-lane eviction and retry, if the required owner lanes remain unavailable, the system MUST raise a recoverable capacity-wait error rather than falling back to legacy allocation.
|
|
|
|
The capacity-wait error MUST include required, available, and deficit page counts by owner lane when those diagnostics are available.
|
|
|
|
The system MUST preserve allocator state when an owner-lane allocation attempt fails without selecting pages.
|
|
|
|
**Rationale:** Owner-lane pressure is lane-specific, not aggregate-capacity-specific. Reporting lane diagnostics preserves scheduler recoverability and prevents legacy allocation from hiding placement bugs."""
|