Softirq:avoid large sched delay from the pending softirqs
RFC PATCH 1/1 Softirq:avoid large sched delay from the pending softirqs
From: jun qian <[email protected]>
When get the pending softirqs, it need to process all the pending softirqs in the while loop. If the processing time of each pending softirq is need more than 2 msec in this loop, or one of the softirq will running a long time, according to the original code logic, it will process all the pending softirqs without wakeuping ksoftirqd, which will cause a relatively large scheduling delay on the corresponding CPU, which we do not wish to see. The patch will check the total time to process pending softirq, if the time exceeds 2 ms we need to wakeup the ksofirqd to aviod large sched delay.
--- kernel/softirq.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/softirq.c +3 -0
@@ -299,6 +299,9 @@ asmlinkage __visible void __softirq_entry __do_softirq(void) } h++; pending >>= softirq_bit; + +if (time_after (jiffies, end) &&need_resched ()) +break ; }if (__this_cpu_read (ksoftirqd) == current)
Signature · 1 line
1.8.3.1
Quoted 23 lines
From: jun qian <[email protected]>
When get the pending softirqs, it need to process all the pending softirqs in the while loop. If the processing time of each pending softirq is need more than 2 msec in this loop, or one of the softirq will running a long time, according to the original code logic, it will process all the pending softirqs without wakeuping ksoftirqd, which will cause a relatively large scheduling delay on the corresponding CPU, which we do not wish to see. The patch will check the total time to process pending softirq, if the time exceeds 2 ms we need to wakeup the ksofirqd to aviod large sched delay.
Signed-off-by jun qian <[email protected]>--- kernel/softirq.c | 3 +++ 1 file changed, 3 insertions(+)kernel/softirq.c +0
-0
kernel/softirq.c asmlinkage __visible void __softirq_entry __do_softirq(void) · line 307
Quoted 9 lines
kernel/softirq.c +3
-0@@ -299,6 +299,9 @@ asmlinkage __visible void __softirq_entry __do_softirq(void) } h++; pending >>= softirq_bit; + +if (time_after (jiffies, end) &&need_resched ()) +break ; }if (__this_cpu_read (ksoftirqd) == current)
I have a small concern about MAX_SOFTIRQ_TIME. The problem is that an "end" time is based on jiffies/tick update, so it depends on CONFIG_HZ value of your kernel.
For example if we have CONFIG_HZ=100, msecs_to_jiffies(2) will return 1. For HZ=100 one jiffie is 10 milliseconds. So we can not rely on it, because of low resolution.
Maybe it make sense to fix it first in order to be at least aligned with "2 milliseconds time limit" documentation?
<snip>
* We restart softirq processing for at most MAX_SOFTIRQ_RESTART times,
* but break the loop if need_resched() is set or after 2 ms.
<snip>
ktime_get()/ktime_before()...?
--
Vlad Rezki
Quoted 37 lines · Uladzislau Rezki
Quoted 24 lines
From: jun qian <[email protected]>
When get the pending softirqs, it need to process all the pending softirqs in the while loop. If the processing time of each pending softirq is need more than 2 msec in this loop, or one of the softirq will running a long time, according to the original code logic, it will process all the pending softirqs without wakeuping ksoftirqd, which will cause a relatively large scheduling delay on the corresponding CPU, which we do not wish to see. The patch will check the total time to process pending softirq, if the time exceeds 2 ms we need to wakeup the ksofirqd to aviod large sched delay.
Signed-off-by jun qian <[email protected]>--- kernel/softirq.c | 3 +++ 1 file changed, 3 insertions(+)kernel/softirq.c +0
-0kernel/softirq.c asmlinkage __visible void __softirq_entry __do_softirq(void) · line 307
Quoted 9 lines
kernel/softirq.c +3
-0@@ -299,6 +299,9 @@ asmlinkage __visible void __softirq_entry __do_softirq(void) } h++; pending >>= softirq_bit; + +if (time_after (jiffies, end) &&need_resched ()) +break ; }if (__this_cpu_read (ksoftirqd) == current)I have a small concern about
MAX_SOFTIRQ_TIME. The problem is that an "end" time is based on jiffies/tick update, so it depends onCONFIG_HZvalue of your kernel.
Quoted 4 lines
For example if we have
CONFIG_HZ=100,msecs_to_jiffies(2)will return 1. For HZ=100 one jiffie is 10 milliseconds. So we can not rely on it, because of low resolution.
good tip. Does this problem also exist in the current code, just like this:
if (pending) {
if (time_before(jiffies, end) && !need_resched() &&
/* low resolution problem */
--max_restart)
goto restart;
wakeup_softirqd();
}Quoted 8 lines
Maybe it make sense to fix it first in order to be at least aligned with "2 milliseconds time limit" documentation?
<snip>
* We restart softirq processing for at mostMAX_SOFTIRQ_RESTARTtimes,
* but break the loop ifneed_resched()is set or after 2 ms.
<snip>
I can't find the snip from the linux/Documentation/, could you please tell me where I can find this snip, thks
Quoted 2 lines
ktime_get()/ktime_before()...?
if the low resolution problem also exists in the above code, i think also need to fix it with using ktime_get()/ktime_before().
Quoted 2 lines
--
Vlad Rezki