misk@sopuli.xyz to Technology@lemmy.worldEnglish · 1 day agoFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.comexternal-linkmessage-square220fedilinkarrow-up1572arrow-down110cross-posted to: framework@lemmy.ml
arrow-up1562arrow-down1external-linkFramework’s first desktop is a strange—but unique—mini ITX gaming PCarstechnica.commisk@sopuli.xyz to Technology@lemmy.worldEnglish · 1 day agomessage-square220fedilinkcross-posted to: framework@lemmy.ml
minus-squarewise_pancake@lemmy.calinkfedilinkEnglisharrow-up12·edit-27 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-squarebrucethemoose@lemmy.worldlinkfedilinkEnglisharrow-up1·48 minutes 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.
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