Ingo, Thomas, all, In an SMP system, tasks are scheduled on different CPUs by the scheduler, interrupts are managed by irqbalancer daemon, but timers are still stuck to the CPUs that they have been initialised. Timers queued by tasks gets re-queued on the CPU where the task gets to run next, but timers from IRQ context like the ones in device drivers are still stuck on the CPU they were initialised. This framework will help move all 'movable timers' using a sysctl interface. Please consider for inclusion into -tip Testing Carried Out: * Kernbench on a 2-package, quad-core machine results are as follows: ----------------------------------------------------------------------- | No. of Threads | Time(s) - Without | Time(s) - With the | | | patches applied | patches applied | ----------------------------------------------------------------------- | 2 | 106.9 | 106.3 | | 4 | 54.7 | 54.4 | | 8 | 31.5 | 31.1 | | 16 | 28.0 | 27.5 | | 32 | 28.1 | 28.9 | ----------------------------------------------------------------------- * I have cross-compiled my patches against alpha architecture in order to test if my patches have any issues for architectures without clockevents support. The patches cross-compile without any issues for alpha architecture, but I need help to test if there is any performance regression. So I'm Cc-ing the maintainers of architectures without clockevents support. The following patches are included: PATCH 1/4 - framework to identify pinned timers. PATCH 2/4 - identifying the existing pinned hrtimers. PATCH 3/4 - /proc/sys sysctl hook to enable timer migration. PATCH 4/4 - logic to enable timer migration. The patchset is based on the latest tip/master. Timer migration is enabled by default. It can be turned off when CONFIG_SCHED_DEBUG=y by echo 0 > /proc/sys/kernel/timer_migration --arun _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
