Sample Header Ad - 728x90

Do kernel threads seem to interfere with full tickless mode?

6 votes
1 answer
2730 views
I'm trying to disable local timer interrupts for low latency. I have full tickless mode enabled in the kernel config and I have the boot parameter nohz_full set for the cores in question. However when I look at the interrupt count through /proc/interrupts I see the local timer interrupts counting up 1000 times a sec per core meaning full tickless isn't working. The tickless mode documentation says that for tickless to work that only one running process needs to be on that core. When I look at top, I see the following under a given core (core 1 in this example): 19 root RT 0 0 0 0 S 0.0 0.0 0:00.00 1 watchdog/1 20 root -2 0 0 0 0 S 0.0 0.0 0:02.15 1 rcuc/1 21 root RT 0 0 0 0 S 0.0 0.0 0:00.04 1 migration/1 22 root -2 0 0 0 0 S 0.0 0.0 0:00.25 1 ksoftirqd/1 23 root RT 0 0 0 0 S 0.0 0.0 0:00.00 1 posixcputmr/1 24 root 20 0 0 0 0 S 0.0 0.0 0:00.00 1 kworker/1:0 25 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 1 kworker/1:0H I do know that some of these are kernel threads. Are these the reason why my full tickless mode isn't working?
Asked by Nathan Doromal (195 rep)
Jun 5, 2014, 07:36 PM
Last activity: Feb 11, 2022, 08:27 PM