[Docs] (P12): the three rows that keep their wait get a ruling with evidence behind it, and the handoff's open op-split question gets its numbers

- What was open: the handoff's 4.3 called ResourceCreate and SetTextureParams "a second problem of
  the same kind, needing its own analysis" and left it there; 5.4 said the per-op split of the
  55,428 waits was never quantified. The measurement committed beside this answers both.
- The ruling (CONTRACT-P5E.md 2.5): ResourceCreate, ResourceRespecify and SetTextureParams stay
  kWaitReply, because each answer carries a fact about the SERVER's record table that the client's
  own tracker provably cannot know. RespecifyOnce says it outright - "the applier's REFUSAL is the
  only signal that says 'I hold nothing for this handle'", which is the scope
  MGPipeApplierReleaseObjectRecords leaves for a served context whose frontend objects live on;
  EmitTextureParams uses its own refusal as the same self-heal trigger; PublishCreate may not take
  the publication latch on a refused create (D-I1/c0b) or the death path emits a resource_destroy
  for a record that does not exist. Unlike the upload half these are not "the emission gate already
  answered it" rows, so removing their waits removes the signal.
- The numbers, both shapes a stitcher produces: an atlas stitch goes 64 -> 0 reply waits; a texture
  per sprite goes 384 -> 320 with ResourceSubData now zero and the remainder all three of those
  rows. So item B hits exactly the shape it was aimed at, and what is left is per-resource /
  per-call rather than per-chunk.
- notes/p12/DEVICELOST-AND-UPLOAD-WAITS.md gains 2.4 with the table and the ruling, and its "second
  problem of the same kind" entry is closed rather than carried; MEASUREMENTS.md records the two
  shapes beside the 1 -> 0 single-upload number.
This commit is contained in:
BZLZHH
2026-09-25 20:17:22 +08:00
parent fa8b500ba8
commit ce0235b190
3 changed files with 43 additions and 4 deletions
+14 -1
View File
@@ -206,7 +206,20 @@ non-wire arm keep the old answer, which is what G1 measures. Gate:
`RemoteClientControls.TextureUploadsStopOwningAReplyOnTheWireArm` reads back the same `wait_replies`
the P65LinkMetrics line prints (`LinkMetricsReplyWaits`), asserting a pure upload moves it by ZERO
while a `resource_create` row still moves it; red-once with the arm test removed is exit 142.
`ResourceCreate` and `SetTextureParams` stay `kWaitReply` — same question, asked per resource and
**`ResourceCreate`, `ResourceRespecify` and `SetTextureParams` stay `kWaitReply`, and that is a
ruling rather than an omission**: each one's answer carries a fact about the SERVER's record table
that the client's own tracker provably cannot know. `RespecifyOnce` (`TextureEmit.h:1332-1356`) says
it in one line - "the applier's REFUSAL is the only signal that says 'I hold nothing for this
handle'", which is the scope `MGPipeApplierReleaseObjectRecords` leaves behind for a served
context whose frontend objects live on; `EmitTextureParams` (`:991-1017`) uses its own refusal as
the same self-heal trigger; and `PublishCreate` (`:1303-1319`, D-I1/c0b) may not take the
publication latch on a create the applier refused, or the death path emits a `resource_destroy` for
a record that does not exist. Removing any of those waits removes the signal, so unlike the upload
half they are not "the emission gate already answered this" rows. Measured split for the two shapes
a stitcher produces (P12, `RemoteClientControls.ReplyWaitsByOpForAnAtlasShapedLoad`): an atlas
stitch - 64 sub-uploads into one level - goes from 64 reply waits to **0**, while a texture per
sprite - 64 textures, 256 `glTexParameteri` - goes from 384 to 320, with the remainder all three of
these rows (create 76, respecify 130, params 130).
per call, analyzed separately rather than swept in here.
### 2.6 Event-ring flow control (ARCHITECTURE §11.7 made real)