| 6 Apr 2026 |
|  Eli Saado changed their profile picture. | 11:04:08 |
| Eli Saado changed their profile picture. | 11:05:03 |
|  ashisgreat joined the room. | 12:20:29 |
| 7 Apr 2026 |
|  @oleg20082009:matrix.org joined the room. | 21:17:58 |
| @oleg20082009:matrix.org left the room. | 21:37:41 |
| 8 Apr 2026 |
|  janusz-bit joined the room. | 06:54:51 |
|  loopunit joined the room. | 07:18:18 |
|  Azthurano joined the room. | 23:18:36 |
| 9 Apr 2026 |
 niklaskorz | https://pixelcluster.github.io/VRAM-Mgmt-fixed/ | 14:09:57 |
| niklaskorz | dmemcg-booster looks trivial to package but lacks a license it seems (and also is of limited use I guess, until the kernel and KDE patches are upstreamed) | 14:18:03 |
 K900 | We have it in Jovian FWIW | 14:19:29 |
| K900 | But we also have the Valve kernel which has had these patches for a long itme | 14:19:52 |
| niklaskorz | interesting, thx! | 14:21:56 |
 anji | VRAM management is definitely something Windows does better. Its vidmm component does a pretty good job keeping the most important allocations in VRAM and evicting everything else if needed. I don't understand the Linux GPU architecture but it would be cool if it had a similar vendor-neutral component to manage system wide allocations.. | 14:46:39 |
 magic_rb | Does nvidia share this problem? Id guess not | 14:56:43 |
| K900 | It does | 15:37:57 |
| K900 | That's what dmemcg is | 15:37:57 |
| K900 | NVIDIA IIRC never evicts VRAM | 15:38:06 |
| K900 | *nvidia proprietary | 15:38:09 |
| magic_rb | Ah thats a bit, weird? | 15:44:36 |
| magic_rb | Ig on my laptop idc since i have an igpu, but on desktop that sounds rough | 15:44:55 |
| magic_rb | As the blog said, chromiums competing with cyberpunk is not great | 15:45:17 |
| K900 | I think it's an EXPORTSYMBOLGPL thing | 15:46:22 |
| K900 | (again) | 15:46:23 |
| magic_rb | With nvidia open that is no longer a concern tho | 15:47:23 |
| magic_rb | Or are you specifically talking about nvidia proprietary closed? | 15:47:38 |
| anji | Ah, so it now can change resource residency on the system level? Is that a recent development (as the blog alludes to)? I've only known it to be mostly a QOS/limiting thing. If it's using cgroups then it's still not quite as sophisticated, as vidmm can do per-allocation heuristics even inside processes. | 15:53:27 |
| K900 | The kernel can already do per-allocation heuristics | 15:53:53 |
| K900 | And does so | 15:53:55 |
| K900 | dmemcg is a way for applications to communicate priority | 15:54:06 |
