32ef5d8db0
It was found during code review that the kernel always try to migrate timers away from idle CPUs to busy CPUs. Real-time CPUs running dpdk polling threads for example, are busy so they are a great candidate to receive timers from idle CPUs (see get_nohz_timer_target() in the kernel sources). It is not clear how this problem can affect real-time applications and KVM-RT. However, for real-time and high-performance the best thing is for a timer to always fire in the CPU where it was created. Resolves: rhbz#1323283 Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> |
||
|---|---|---|
| .. | ||
| realtime-variables.conf | ||
| script.sh | ||
| tuned.conf | ||