Source

Thread

1/ @NOTimothyLottes

Linux by default doesn’t allow any increase in scheduling priority. Users need to manually setup special user|group with elevated rights. Also system calls that try elevated scheduling don’t clamp, instead they fail -EPREM if out of bounds. So all around a pain in the ass.


2/ @NOTimothyLottes

I’m a little lazy right now and don’t feel like trying SteamOS big picture mode to see what the default ulimits are. Curious what they allow.

3/ @NOTimothyLottes

Linux priority workarounds
(a.) Use getrlimit() to get {soft,hard} limits
(b.) Use setrlimit() to set ‘soft=hard’ limit
(c.) Then set priority or nice based on new soft limit


4/ @NOTimothyLottes

I don’t do one-time global priority maximums, just in case someone sudo’s higher priority hard limit dynamically it should pickup the new limit.

5/ @NOTimothyLottes

Also while on setrlimit, I also bump up the RLIMIT_MEMLOCK to it’s maximum just in case before the mlockall().

0 items under this folder.