A full task-isolation mode for the kernel

Posted Apr 6, 2020 23:15 UTC (Mon) by f18m (guest, #133856)
In reply to: A full task-isolation mode for the kernel by ncm
Parent article: A full task-isolation mode for the kernel

I fully agree with ncm: what's the sense of isolating a CPU core other than the need of using it without any sort of interrupt to emulate a real-time OS ?

However I'm unsure whether having the kernel deciding that a taskset should be "fully isolated" after a few milliseconds of zero-system-calls...

Anyway this patch set would be greatly useful to e.g. DPDK applications, which are mostly often using isolcpus and nohz options already.
Looking forward for it!

I'd also love to have this RTOS-like as a post-boot option somewhere (maybe a sysctl setting?) rather than being forced to create scripts that must interact with the bootloader (GRUBv1, GRUBv2, etc) to deploy a new Linux boot option... moreover the reboot required to apply this change may not be acceptable in some contexts...

A full task-isolation mode for the kernel

Posted Apr 7, 2020 1:13 UTC (Tue) by flussence (guest, #85566) [Link]

“Soft” isolation is still useful for HPC work, where you'd like to have something stronger than SCHED_BATCH, but nobody's going to end up taken away in an ambulance if it only gets 99.99% of the CPU.