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

[phoronix]

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

As expected, minutes ago Linus Torvalds just released the Linux 6.12 kernel as stable. Linux 6.12 brings many new features, new hardware support, and is rounded out by the fact of expected to become this year's Long Term Support (LTS) kernel version...

https://www.phoronix.com/news/Linux-6.12-Released

[dimko]

I tried pre-releases, with real time switching enabled. it hurt performance pretty bad in games.
Some serious frame drops happened. Will try release now...

[nuetzel]

Michael

When w'll see your 'announced' RT on/off comparison?
Maybe on midsize Ryzen (without 3D V-Cache).

[F.Ultra]

I tried pre-releases, with real time switching enabled. it hurt performance pretty bad in games.
Some serious frame drops happened. Will try release now...

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.

[skeevy420]

I tried pre-releases, with real time switching enabled. it hurt performance pretty bad in games.
Some serious frame drops happened. Will try release now...

Well, that's to be expected. Games don't need real time performance since they can spawn a lot of processes. 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.

The way I understand it, RT is best for smaller, headless setups where you have the one task that needs to be done at the expense of anything else; like in an embedded OS controlling a LIDAR sensor.

[Quackdoc]

Can't wait for arch to ship it, tired of building my own kernel for scx, It is quite literally a game changer.

[erniv2]

Well, that's to be expected. Games don't need real time performance since they can spawn a lot of processes. 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.

The way I understand it, RT is best for smaller, headless setups where you have the one task that needs to be done at the expense of anything else; like in an embedded OS controlling a LIDAR sensor.

Yes thats the question that windows users allways want to know, they tried other MTU´s , disable nagling and whatever tweak they came across, end of the story is Einstein.

It´s the same with cars a 2 ton car will allways consume more energy than a 1 ton car, you cant change it if your cpu uses this watt for this process it will allways use that, you can trick with the resistence in the material, and the voltages etc. but in the end you cant trick the physics.

If that electron wants to move from one place to the other place you have to pay the price, there is no free meal.

Edit to that it´s a complete lie that you can reduce power consuption with drivers or so, the power comsumption is based on the needs of the cpu if there is high demand it´s high power, thats whats pretty much reflectet in the drivers, but if your cpu runs 100% all the time you just dont need it.

And no driver will change the outcome of it if your cpu needs x cylces it needs x clycles and no matter of it runs at 1v at 4ghz or 1.25v at 5ghz.

It is the same cause 1.25v at 5 ghz is exactly the same energy output like 4ghz at 1v , given that it´s the same resitence it will be the same watts, surprise einstein.

The same output for the workload done ~~

[intelfx]

I tried pre-releases, with real time switching enabled. it hurt performance pretty bad in games.
Some serious frame drops happened. Will try release now...

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

[billyswong]

Edit to that it´s a complete lie that you can reduce power consuption with drivers or so, the power comsumption is based on the needs of the cpu if there is high demand it´s high power, thats whats pretty much reflectet in the drivers, but if your cpu runs 100% all the time you just dont need it.

And no driver will change the outcome of it if your cpu needs x cylces it needs x clycles and no matter of it runs at 1v at 4ghz or 1.25v at 5ghz.

It is the same cause 1.25v at 5 ghz is exactly the same energy output like 4ghz at 1v , given that it´s the same resitence it will be the same watts, surprise einstein.

The same output for the workload done ~~

You can't reduce the power consumption for the same amount of work done without replacing the hardware (or inventing new algorithm to compute the same problem more efficiently), but you can reduce the power consumption per unit of time by lengthening the time used in doing the work, or reduce the amount of work (e.g. render lower quality graphics in gameplay)

[mobadboy]

Real-Time Capabilities

bloat

Sched_Ext

bloat

More AMD RDNA4

BLOAT

LoC only goes up, never goes down

unless planned obsolescence strikes and they remove yet another critical driver