message GpuReport

The configured speculative ceiling, and what it comes to once the in-use set has taken its share of imageBudgetBytes. The second is the number eviction actually runs against, and it reaches zero first.

Foreign (mapped-in client) bytes, and bytes waiting for a frame to retire.

What the driver attributes to this process, what it would allow, and what the card has. The number to compare against nvidia-smi.

Standalone images something is currently pointing at, and the ceiling they are counted against. The two halves of the cache behave completely differently and a single figure hides which one is the problem: dormant bytes go when the number says so, in-use bytes are a texture id a client is drawing with and there is no way to ask for them back.

What the entries below add up to: this process's own memory, without the client buffers it merely maps.

Samples every render target is allocated with, and the most the device would allow. Two numbers because the first being the second is a choice, and it multiplies the two largest categories in the report.

Whether the cache is holding anything on spec at all. A zero allowance means two unrelated things — the in-use set has taken the whole budget, or the cache has been told to stand down because a client is being scanned out — and a reader cannot tell them apart from the numbers.

Cache totals, which are the whole cache rather than only the entries sent.

Largest first, and capped — a cache with thousands of entries would make this message the reason for the next report.

What the allocator has handed out, and the device-memory blocks it holds to serve that. The difference is slack it could give back.