CPU isolation


One Line Summary

Why and how to efficiently dedicate a CPU to a single task through CPU isolation.


In SMP, tasks that want to have a dedicated CPU for their job could find a better optimized environment. Even though we have only one task running on a dedicated CPU, interrupts have yet to be serviced, deferred jobs need to be handled, and rcu quiescent states and callbacks still have to be managed, etc…

But some of this noise can be avoided to provide the CPU isolation for the task: device interrupts can be migrated, timer interrupts servicing and signaling rcu quiescent states can be partly avoided, etc…

Such isolation and irq noise reduction is likely to improve the average latency on high priority tasks.

This talk aims to present the upside of getting the CPU isolation feature into a proper shape and what kind of technical problems that induces.


  • Biography

    I have been working on the Linux Kernel for two years, mainly in topics like tracing and profiling. Let’s say instrumentation.

    These days I work mostly to enhance perf events and try to unify ftrace and perf into a single powerful instrumentation subsystem.

Leave a private comment to organizers about this proposal