No fixed object count: the handle index, the VM's mappings and ranges,
a client's entries and its BO views grow with memory only. Queues grow
as msm's submitqueues do; each client owns a 2^32 range of the shared
queue space. Jobs are bounded by ring space: a full ring answers
kIOReturnBusy, as msm waits for room. A BO is limited by the client's
GPU address window, which Query reports as max_bo_bytes; the 256 MiB
budget and the ABI's queue and size constants are gone.
ABI version 2 raises the IB list to 128 entries, so the ring prologue
(cache flush, idle wait, thread switch) runs once per frame instead of
once per 16 IBs. The submit lists live in the client and submit objects
instead of the kernel stack. The stall handler drops the translations and
gives the write pointer again after 10 waits; the IB counts per submission
are recorded.
- Four client windows: the render server keeps 1 GiB, and the
wallpaper, icon and widget processes share the rest of the aperture
(170 MiB each).
- A client that owns no queue range yet is no longer refused by
setScope, held up in close or waited on in releaseAll because the
render server has jobs in flight in the default range 0 (int-200).
New regression block in the user-client host test.
- BoCpuUnmap keeps the shared CPU view while another mapping lease of
the same BO is held; dropping it unmapped the other holder's pages
and crashed the render server in vkCmdCopyBuffer (int-177).
- Diagnostics: the reason the latest mount failed, mappings that fall
outside a client window, a text row per non-render-server process
and a name for the mailbox poller thread.
The SMMU tables and ring/fence/SQE buffers no longer come from the
write-combined pool, so CPU table walks stay cached. The published
service keeps one user-client core per connection: the render server
gets the 1 GiB window at 0x20000000 and two other processes 256 MiB
each, with their own queue ranges and teardown.