| 9 Apr 2026 |
 K900 | The kernel doesn't know which processes are more important | 16:00:17 |
 anji | I guess "the kernel" here just means the lower level mechanics not Mesa/dmemcg etc | 16:00:25 |
| K900 | Neither does Mesa really | 16:00:33 |
| K900 | The reason you need the KDE glue is because the desktop environment is what actually knows that information | 16:00:51 |
| anji | What is foreground yes. But internal prioritization mostly depends on the work submission, resource types, etc. UMD/KMD stuff. | 16:02:10 |
| K900 | The kernel does know and use that | 16:02:43 |
| anji | Regardless foreground application prioritization really is the most essential. So I hope all that can come together soon | 16:02:45 |
| anji | What system in the kernel does this? As far as I know dmemcg is just a small set of APIs to control vram priorization in regions? It's not a full system level memory manager is it? | 16:05:41 |
| K900 | It's not, the actual eviction heuristics are in the drivers | 16:06:17 |
| anji | Right. So different drivers have to make different prioritization decisions without necessarily seeing the total system picture. | 16:06:48 |
| anji | Which is different than vidmm | 16:06:55 |
| anji | I'm not arguing Linux necessarily needs such a complex video memory manager btw. Just trying to understand what is currently there and how it works. And it's cool to see progress here, because vram overcommit is/was pretty bad. | 16:13:17 |
 niklaskorz | The Nvidia open kernel modules support Linux heterogenous memory management but I don't know if this automatically entails memory eviction from vram to ram | 23:17:43 |
| 10 Apr 2026 |
 ccicnce113424 | https://github.com/NixOS/nixpkgs/pull/498612 | nixos/nvidia, linuxPackages.nvidia-x11: split proprietary kernel modules, use source-built ICDs, write params via modprobe
Can you have a look? | 09:07:01 |
| K900 | You probably want to talk to the CUDA folks for this tbh | 09:07:53 |
| K900 | They're de facto the ones in charge of the Nvidia proprietary stack | 09:08:01 |
| niklaskorz | Gaetan already reviewed it | 09:08:13 |
| niklaskorz | well, at least he reacted on the PR | 09:08:35 |
| K900 | I mean they should still be the ones to merge it probably | 09:10:11 |
| niklaskorz | agreed, I've request the team for review on the PR | 09:10:59 |
| niklaskorz | * agreed, I've requested the team for review on the PR | 09:11:15 |
| niklaskorz | I'll also smoke test the changes on my system in a moment | 09:15:31 |
| K900 | I don't have Nvidia hardware | 09:17:14 |
| K900 | So I can't help here | 09:17:19 |
|  ladas552 joined the room. | 20:51:52 |
| 11 Apr 2026 |
| anji | I'm curious if this section of the wiki is still relevant: https://wiki.nixos.org/wiki/Steam#Gamescope_HDR
I've been trying (and failing) to get HDR to work in Steam games for some time. On NixOS stable. This section recommends the "gamescope-wsi" package but it seems like this is now just the "gamescope" package? | 01:41:01 |
| anji | * I'm curious if this section of the wiki is still relevant: https://wiki.nixos.org/wiki/Steam#Gamescope_HDR
I've been trying (and failing) to get HDR to work in Steam games for some time. On NixOS stable.
Specifically: This section recommends the "gamescope-wsi" package but it seems like this is now just the "gamescope" package? | 01:44:42 |
| anji | Huh. Changing from gamescope to gamescope-wsi does seem to work. I guess I don't understand how search.nixos.org works then. I thought these two packages were somehow aliases but it does actually change something. Anyway, that wiki entry is 👍️ | 01:53:38 |
|  Lukas joined the room. | 02:15:05 |
 arcayr | i searched for it and can see it in both 25.11 and unstable | 03:33:02 |
