- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
You must log in or # to comment.
Seemingly 2 other people worked on it as well, one from Red Hat and one from Intel.
Also bear this in mind:
All the user-space utilities hard-depend on systemd. Without systemd, you’d need to write your own utilities that make use of my kernel patches. Something needs to manage cgroups in your system, and that something needs to enable the right cgroup controllers and set the right limits (see also the long-winded explanation about how this works).
Maybe my GTX 1650 (4GB VRAM) gpu is not useless.
Archlinux BTW. When?
It’s on the AUR but you need a patched kernel which you can grab from catchyOS
Instructions are in the developer’s blog post: https://pixelcluster.github.io/VRAM-Mgmt-fixed/
Q: I use another Arch-based distro! What now?
The
dmemcg-boosterandplasma-foreground-boosterutilities are available in the AUR as well (plasma-foreground-booster carries the package nameplasma-foreground-booster-dmemcg), so you can install them from there.For the kernel side, you can either use the CachyOS kernel package on a non-CachyOS system by retrieving the package from their repository, or you can compile your own kernel. Installing
linux-dmemcgfrom the AUR will compile the development branch I used to develop this. Being a development branch, this carries the risk of some stuff being broken, so install at your own risk!If you want to apply the kernel patches yourself, you need these six .patch files: [links in blog]
I’m not sure how easily they apply on specific kernel versions, but feel free to leave a comment if you run into issues and I’ll try to help out.
Thank you for looking into, appreciate the help. I wanted to read the article later to figure out the details. I think a custom Kernel goes a bit too far for my taste, so will then wait until its officially integrated.
This is amazing because I have a GTX1660 and just switched to Catchy.
I think RADV Vulkan means its for AMD, not Nvidia. Nvidia has their own set of drivers. Unless I am misunderstanding here something.
That is correct, the fix targets the AMDGPU kernel driver so nvidia users will have to wait/implement it ourselves.
So this is just for AMD cards, correct?
She answered that in her blog post that the Phoronix article links to:
Which GPUs does this work with? Is it only AMD GPUs?
Whether or not your GPU can benefit from it depends on the kernel driver - more specifically, whether it sets up the dmem cgroup controller.
amdgpu and xe both have support for the dmem cgroup controller already. In theory, Intel GPUs running the xe kernel driver should benefit as well, although I’m not sure anyone tested this yet.
For nouveau, I have sent a patch for dmem cgroup support to the mailing lists. This patch is also included in my development branch, so if you use my AUR package it should work. In other cases, you will need to wait for the patch to be picked up by your distribution, or apply it yourself.
The proprietary NVIDIA kernel modules do not support dmem cgroups yet, so this won’t work there.
patches to the Linux kernel and KDE
I think currently it might only work for AMD, but I think Nvidia could take advantage of it without too much work
RADV is driver for AMD. So I assume it is for AMD cards only.
Cool, that was my assumption but I’m sort of a noob so I didn’t know if the plasma bit was card agnostic or not.
Also the linked articles headline is
Fixing AMDGPU’s VRAM management for low-end GPUs
And in the entire article the word
nvidiais not found once.
Valve are cool, love that they do this.
I know it helps them, but they have done so much for Linux gaming it’s incredible.
Just wish it was coming from a non-commercial entity. Puts a sour note on the status of Linux gaming that a for-profit entity is the only one out there making meaningful progress.
Better than the ones that take and give nothing back though
on the flip, it’s heartening to see an influential company like Valve actually not being shitty.
It’s either slave labor or there is SOME form of for profit company is involved somewhere in the chain. Those are basically your two options.
Even purely free work given willingly in someone’s free time is still supported by proxy of some form of corporate entity. No one lives for free.
All that matters is the license. If you care any more beyond that your either stupid or dealing with active Nazis. And I don’t see any Nazis in valve so…
Lots of for-profit commercial entities contribute to open source projects.
The code they’re contributing is covered by the same license as the code contributed by volunteer developers.
I understand why we should be cautious about these things, but the current situation is that Valve is contributing a lot and their contributions are open source. Yeah, they’re doing it for a profit motive, but not to the point where they’re trying to kill open source projects or hide the updates behind proprietary binaries.
Valve is, currently, not being evil. GabeN has plenty of yacht money.
Gabe really is one of the exceptions that not all CEOs are evil bastards.
Right, but we look at examples like Chromium and we can see where there is still so much potential for things to go sideways. GabeN and his yacht could sink to the bottom of the sea and his estate sells control of Valve to someone less benevolent.
A commercial entity that has enough control over a project pushes the direction of that project in their favor. And sure you can fork a FOSS project at any time, but once the commercialized version has enough saturation, user inertia and lack of experienced developers to take that initiative often prevents alternatives from achieving success.
I think the big difference is Valve isn’t really in control of many of the projects they’re funding, they’re mostly just bringing in existing maintainers as contractors and letting them work on what they want.
Chromium on the other hand has always been something Google has explicitly been in direct control of.
Yup, long as it’s copyleft (GPL)) open source, I don’t care if it’s microslop paying.
That said, watch out for a new wave of EEE (embrace, extend, extinguish) using unmaintainable AI code, and be ready to fork.
Valve, not so much.
Yeah, exactly. If they ever try anything you can just fork from just before that update.
While they play nice, their contributions are welcome and improve software for everyone.
Unfortunately it’s very hard to fund non profit work in the current economy.
