A full task-isolation mode for the kernel

Posted Apr 12, 2020 16:57 UTC (Sun) by dave4444 (subscriber, #127523)
Parent article: A full task-isolation mode for the kernel

Looks like some good progress here, but what about events that may (or may not) be out of the control of the kernel? Such as:

SMM/SMI/NMI on that CPU, this may not be preventable, but could it be detected?

ECC errors can cause very unpredictable slowdowns (especially correctable ones).

Some applications require more than just a CPU core's resources to itself, memory contention (L3, or beyond), common IO paths etc... can produce slow or even starved applications. Another app on another core can hog and consume L3 and DRAM bandwidth at the detrement to others for example.

A full task-isolation mode for the kernel

Posted Apr 15, 2020 18:43 UTC (Wed) by jithu83 (guest, #134793) [Link]

> Some applications require more than just a CPU core's resources to itself, memory contention (L3, or beyond), common IO paths etc... can produce slow or even starved applications. Another app on another core can hog and consume L3 and DRAM bandwidth at the detrement to others for example.

X86_CPU_RESCTRL kernel config option does provide some fine grained control over memory bandwidth, L2/L3 cache partitioning/locking etc. This is available only on certain newer processors and requires additional effort to correctly provision these to the appropriate process etc