realtime: use skew_tick=1 in kernel cmdline
By default the timer tick will fire at the same time on all CPUs. This causes the jiffies_lock to get contended in the real-time kernel, as it's a raw spinlock. skew_tick=1 causes the timer tick to fire at different times on all CPUs, fixing the contention. Note skew_tick=1 usage is going to be propagated to the NFV profiles as well. Resolves: rhbz#1447938 Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
This commit is contained in:
parent
fdff5f15b9
commit
9bc020df37
1 changed files with 1 additions and 1 deletions
|
|
@ -36,7 +36,7 @@ kernel.timer_migration = 0
|
|||
/sys/devices/system/machinecheck/machinecheck*/ignore_ce = 1
|
||||
|
||||
[bootloader]
|
||||
cmdline=isolcpus=${isolated_cores} intel_pstate=disable nosoftlockup
|
||||
cmdline=isolcpus=${isolated_cores} intel_pstate=disable nosoftlockup skew_tick=1
|
||||
|
||||
[script]
|
||||
script = ${i:PROFILE_DIR}/script.sh
|
||||
|
|
|
|||
Loading…
Reference in a new issue