Blame
| 6531e5 | deseven | 2025-07-03 08:57:20 | 1 | # 110GB of VRAM |
| 2 | ||||
| 3 | :::info |
|||
| 4 | # Notice |
|||
| 5 | This is possible on Linux only and wasn't yet tested by me. Sources: |
|||
| 6 | - https://community.frame.work/t/framework-laptop-13-ryzen-300-configuring-graphics-memory/65389/16 |
|||
| 7 | - https://blog.hjc.im/strix-halo-local-llm.html |
|||
| 8 | ::: |
|||
| 9 | ||||
| 10 | ### Module Options |
|||
| 11 | `/etc/modprobe.d/vram.conf`: |
|||
| 12 | ```bash |
|||
| 13 | options amdgpu gttsize=110000 |
|||
| 14 | options ttm pages_limit=26856000 |
|||
| 15 | options ttm page_pool_size=26856000 |
|||
| 16 | ``` |
|||
| 17 | ||||
| f685c3 | deseven | 2025-07-12 11:54:40 | 18 | Note that **110GB is NOT a hard limit**, you can allocate more, as long as there is enough memory for the OS to work. |
| 19 | ||||
| 6531e5 | deseven | 2025-07-03 08:57:20 | 20 | ### Performance Concerns |
| 21 | There were reports that when IOMMU is active and the VRAM is being set on the OS level, the memory latency becomes too high. To prevent this, either disable IOMMU in the BIOS or set `amd_iommu=off` it kernel boot params. |
|||
| 22 | ||||
| 23 | ### Relevant Pages |
|||
| 24 | - [[Guides/AI-Capabilities]] |