Shared GPU memory (as described in that article) is just how Windows decided to solve the problem of oversubscription of VRAM. Linux solves it differently (looks like it just allocates what it needs in demand and uses GART to address it, but I would like to know more).
So I’m curious what you mean when you say you miss it. Are you having programs crash OOM when running on Linux? Because that shouldn’t be happening.
It’s not ideal to be relying on shared gpu mem anyway (at least in a dgpu scenario). Kinda like saying you have a preference on which crutches to use.
There is one game called Cities: Skylines 2 that always fills up my VRAM, so yeah, I’m getting an OOM, but on the VRAM (I have GTX 1660super with 6 gigs of VRAM and I have 32 gigs of system RAM). I encourage you to try playing this game with a moderately sized city and with this GPU.
Shared GPU memory (as described in that article) is just how Windows decided to solve the problem of oversubscription of VRAM. Linux solves it differently (looks like it just allocates what it needs in demand and uses GART to address it, but I would like to know more).
So I’m curious what you mean when you say you miss it. Are you having programs crash OOM when running on Linux? Because that shouldn’t be happening.
It’s not ideal to be relying on shared gpu mem anyway (at least in a dgpu scenario). Kinda like saying you have a preference on which crutches to use.
There is one game called Cities: Skylines 2 that always fills up my VRAM, so yeah, I’m getting an OOM, but on the VRAM (I have GTX 1660super with 6 gigs of VRAM and I have 32 gigs of system RAM). I encourage you to try playing this game with a moderately sized city and with this GPU.