Allocation path behind MTLResourceStorageModeShared buffers (IOGPU vs IOSurface)
Parent: Mac local LLMs: Memory and wired limits · Published reference · snapshot 2026-10-05
↓ Facts as markdownall context files
The macOS `footprint` tool lists MLX Metal allocations under a region named "IOAccelerator (graphics)", so the allocation is accounted as graphics (IOAccelerator) memory, not as a plain malloc or IOSurface region.
These notes link each claim to its source. A source may be a research report hosted on this site rather than the primary document. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Facts
- The macOS `footprint` tool lists MLX Metal allocations under a region named "IOAccelerator (graphics)", so the allocation is accounted as graphics (IOAccelerator) memory, not as a plain malloc or IOSurface region. [source]
- The same tool output marked those pages "all DIRTY, 0 reclaimable". [source]
- Whether an IOSurface sits underneath is not stated in any source read. [source]
- `footprint <pid>` on an M5 Max running MLX 0.32.0 showed 109 GB under "IOAccelerator (graphics)", all dirty, with phys_footprint 110 GB. [source]
- The existing dossier's allocation-path open question is narrowed to the IOAccelerator (graphics) family; IOSurface is not named in this footprint listing. [source]
Children
- No children recorded.