mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-08 10:33:24 +09:00
swung0x48
a63577354d
R-10's "P5 does not chunk (R-10)" wording predates the stage chunk budget: buffer content ranges are cut at MGPipeStageChunkBytes() (1e7c372e) and a texture level at whole-width slabs (9469d48e), so the claim is false for the two rows that can outgrow SEG_STAGE - and these messages are what a bring-up reads. - PipeWireEncoder::StageAllocate's two Fatal{RingOverrun, "SEG_STAGE"} sites now say what reaching them means: a blob is staged whole, a row that cuts its content at the stage chunk budget never arrives, so this is a record type with no cut or a piece still larger than the arena. - EncodeRecord's MaxRecordBytes arm says the bound is about the record's own bytes - the stage chunk budget cuts blobs, not a header, payload or inline tail - and keeps the integrator decision it names. - Comments in PipeWireCodec.h, EmitTables.cpp's maxrecop line, Config.h's STAGE_MB knob, PipeStats.h's MaxRecordBytes gauge, SplitRuntimePeek.h and WireLedgerChecks.h said P5 does no chunking; they now say what is cut and what is not. - PipeWireCodecTest.ARecordLargerThanHalfTheRingIsFatalRingOverrun asserts the new diagnostic text instead of "does not chunk (R-10)".