Linux 6.12 Released With Real-Time Capabilities, Sched_Ext, More AMD RDNA4 & More

[Volta]

blah blah blah

Bot. Mobadbot.

[dlq84]

bloat



bloat



BLOAT

LoC only goes up, never goes down

unless planned obsolescence strikes and they remove yet another critical driver

Birdies latest troll account?

[kokoko3k]

bloat

My realtime audio setup is quite happy of the bloat, hopefully this will allow me to strip a boot option and a kernel from the system.

Wait, thats a de-bloat!

[dimko]

throughput will be worse since that is the tradeoff, so if your games where already maxing your cpu then that might explain the frame drops, otherwise rt will mostly only help with frametime if you also run other applications at the same time as the game.

I was not very clear. I don't mind overall FPS drop. What I did want is increase in overall responsiveness and higher lower one percent. Also better priority handling, cause current one in Linux is pretty bad when comes to desktop.(for example, play game + compile something)

[Volta]

I was not very clear. I don't mind overall FPS drop. What I did want is increase in overall responsiveness and higher lower one percent. Also better priority handling, cause current one in Linux is pretty bad when comes to desktop.(for example, play game + compile something)

Playing a game when compiling something is not a desktop thing. I recommend to check how no RT 6.12 behaves. It increased FPS in Cyberpunk by a large margin in comparison to 6.11 and Windows. I can easily play on high details now and game is perfectly smooth. On winblows it's slow even on medium settings.

[dimko]

Which one of those 50 some odd processes that the game spawns and was given RT priority needs to have the most RT priority? Audio? Graphics? The compressor accessing the archives the game's files are stored in? The compositor? Reshade? Something else? Now we've delved into a situation where we might need a specialized RT scheduler....

Instead of things being completed in the order the game expects them to be completed in, something is given RT priority to keep on keepin on which prevents other necessary things from running because they have a lower priority and all that gums up the works. At least that's been my experiences with RT gaming and Wine usage over the past decade.

I was not particularly with good with description of my problem.

I have 32 core CPU(16 with hyper threading), games I play often don't even use half of that.
Yesterday I checked Fallout 4 with r12+, problem is that there is massive frame drop once every a few seconds. Hick up, if you like.
I have 64 gig of ram and an SSD, I increased my Wayland priority as well, as well as Pulseaudio. Hick ups were still there. Nothing else but gnome Wayland running in background on my linux Gentoo.
Hardware wise, I seriously doubt there were bottle necks, like 50 processes you described. Nothing else was running on OS.
Non RT kernels don't have this issue. Hence I believe RT is doing something wrong.

I tried FIFO and Round Robin. I did not try deadline since I had some weird permission issues with it. Looks like sudo doesn't like it somehow.

[dimko]

Shocking. Who would've thought that RT is not for games or anything of that sort.

It's not supposed to hurt, right?

[dimko]

Playing a game when compiling something is not a desktop thing. I recommend to check how no RT 6.12 behaves.

It is, on Gentoo
And I will check out later non RT for obvious bugs somewhere, out of curiosity. If I don't forget later.

[FPScholten]

I was not particularly with good with description of my problem.

I have 32 core CPU(16 with hyper threading), games I play often don't even use half of that.
Yesterday I checked Fallout 4 with r12+, problem is that there is massive frame drop once every a few seconds. Hick up, if you like.
I have 64 gig of ram and an SSD, I increased my Wayland priority as well, as well as Pulseaudio. Hick ups were still there. Nothing else but gnome Wayland running in background on my linux Gentoo.
Hardware wise, I seriously doubt there were bottle necks, like 50 processes you described. Nothing else was running on OS.
Non RT kernels don't have this issue. Hence I believe RT is doing something wrong.

I tried FIFO and Round Robin. I did not try deadline since I had some weird permission issues with it. Looks like sudo doesn't like it somehow.

The problem is clear, realtime systems prioritize running code. This is done in expense of I/O operations like loading data from disk. Those hickups likely appear because of the game expects the data to be available before the code needs it. This is not how RT works. The data will be fetched when asked, not before, not after. The code can continue after the data has been fetched. This leads to predictable handling of code and data and is exactly why applications on RT systems need to be written with RT in mind.

Done properly this can reduce or rather "produce" less or predictable latency for processes that need this. (like for example audio processors).

Applications that are not written for RT can produce unexpected behavior, crashes or completely hog the cpu, rendering everything else unusable.

The low latency kernel is perhaps what you need, which is not realtime, that you probably do not need at all.

[cl333r]

I have 32 core CPU(16 with hyper threading), games I play often don't even use half of that.
I have 64 gig of ram and an SSD, I increased my Wayland priority as well, as well as Pulseaudio. Hick ups were still there.

I think you deserve a better PC, this one is pretty old and slow. When you buy a new one please don't throw this one to the landfill, I'll give it to a local charity for blind and deaf children from Afghanistan