Skip to content

Softirq:avoid large sched delay from the pending softirqs

[email protected] lkml oe-lkp 6 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v7 Latest4 patches 20 repliesIn review
  2. v61 patch 8 repliesSuperseded
  3. v41 patch 8 repliesSuperseded
Earlier versions · 3
VersionPostedPatchesRepliesStatus
v31 patch2 repliesSuperseded
v2 RFC1 patch8 repliesSuperseded
v1 RFC1 patch2 repliesSuperseded

Patches in v7 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4softirq: Use sched_clock() based timeoutkernel/softirq.c+4 -31 reply
2/4softirq: Factor loop termination conditionkernel/softirq.c+25 -192 replies
3/4softirq: Rewrite softirq processing loopkernel/softirq.c+6 -100 replies
4/4softirq: Allow early break the softirq processing loopkernel/softirq.c+91 -2217 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v7 yet.

Read the v7 thread

Cover letter [PATCH V7 0/4] 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.

jun qian (4):
softirq: Use sched_clock() based timeout
softirq: Factor loop termination condition
softirq: Rewrite softirq processing loop
softirq: Allow early break the softirq processing loop

 kernel/softirq.c | 168 +++++++++++++++++++++++++++++++++++++++----------------
 1 file changed, 120 insertions(+), 48 deletions(-)
Signature · 1 line
1.8.3.1