@[email protected] to TechnologyEnglish • 1 day agoFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.comexternal-linkmessage-square235fedilinkarrow-up1595arrow-down110cross-posted to: [email protected]sffpc[email protected][email protected][email protected]
arrow-up1585arrow-down1external-linkFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.com@[email protected] to TechnologyEnglish • 1 day agomessage-square235fedilinkcross-posted to: [email protected]sffpc[email protected][email protected][email protected]
minus-square@[email protected]linkfedilinkEnglish17•edit-213 hours agoQuestion about how shared VRAM works So I need to specify in the BIOS the split, and then it’s dedicated at runtime, or can I allocate VRAM dynamically as needed by workload? On macos you don’t really have to think about this, so wondering how this compares.
minus-square@[email protected]linkfedilinkEnglish1•6 hours agoIt will most likely be dynamic, with the option to statically set it.
minus-square@brucethemooselinkEnglish2•7 hours agoOn my 7800, it’s static. The 2GB I allocate is not usable for the CPU, and compute apps don’t like it “overflowing” past that. This is on Linux, on a desktop, ASRock mobo. YMMV.
Question about how shared VRAM works
So I need to specify in the BIOS the split, and then it’s dedicated at runtime, or can I allocate VRAM dynamically as needed by workload?
On macos you don’t really have to think about this, so wondering how this compares.
It will most likely be dynamic, with the option to statically set it.
On my 7800, it’s static. The 2GB I allocate is not usable for the CPU, and compute apps don’t like it “overflowing” past that.
This is on Linux, on a desktop, ASRock mobo. YMMV.
It’s typically dynamic