Technology

40289 readers

364 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago

MODERATORS

TheRtRevKaiser@beehaw.org

alyaza@beehaw.org

gyrfalcon@beehaw.org

SemioticStandard@beehaw.org

coldredlight@beehaw.org

rs5th@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

The search for the correct amount of split-lock misery [Linux] (lwn.net)

submitted 6 days ago by Toes@ani.social to c/technology@beehaw.org

4 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] jarfil@beehaw.org 2 points 6 days ago (1 children)

The new kernel.split_lock_mitigate knob, if set to zero, will disable the penalization of processes using split locking (while retaining the warning sent to the system log)

Sounds to me like it's fixed. WINE could follow dmesg, and show a popup with recommendations when it detects one of its processes is getting throttled.

[–] tal@lemmy.today 2 points 6 days ago (1 children)

It still has the performance impact for the rest of the system if one re-enables it.

[–] jarfil@beehaw.org 2 points 6 days ago

As long as you can re-disable it after playing the game...

I know, all background processes get impacted during gameplay, but that was the case already. The popup can explain the tradeoff, and who's to blame (game dev).