[[Linux sys programming]] explains several techniques to subvert OS resource-allocation decisions. Relevant to performance-critical apps.
P275 mlockall(). A Real time app could benefit from locking its entire memory pages into physical RAM, i.e. disable swapping and eliminate
P173 sched_setaffinity(). A strongly cache-sensitive app could benefit from hard affinity (stronger than the default soft affinity), which prevents the kernel scheduler migrating the process to another
[[The Linux Programmer’s Toolbox]]. A write-only variable will be removed by the compiler’s optimizer, but such a variable could be useful to debugger. I read somewhere that you can mark it volatile — subversive.
Any way to prevent “my” data or instruction leaving the L1/L2 cache?
Any way to stay “permantly” in the driver’s seat, subverting the thread scheduler’s time-slicing?