[lkml]   [2010]   [May]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[patch 3/7] softirq: avoid softirq_work_list for SCHED_SOFTIRQ when sent remotely
There is no need to add the SCHED_SOFTIRQ work to the softirq_work_list
when sent remotely. This is because any pending work associated with
SCHED_SOFTIRQ need not be migrated to a new cpu when the current cpu is
going down etc.

Also I am not sure how this softirq_work_list works for other softirqs.
I don't see anyone removing the list entries from the softirq_work_list
after it is handled on a remote cpu.

For now, just skip it for SCHED_SOFTIRQ.

Signed-off-by: Suresh Siddha <>
Cc: David S. Miller <>
Cc: Jens Axboe <>
kernel/softirq.c | 5 +++++
1 file changed, 5 insertions(+)

Index: tip/kernel/softirq.c
--- tip.orig/kernel/softirq.c
+++ tip/kernel/softirq.c
@@ -557,6 +557,11 @@ static void __local_trigger(struct call_
struct list_head *head = &__get_cpu_var(softirq_work_list[softirq]);

+ if (softirq == SCHED_SOFTIRQ) {
+ raise_softirq_irqoff(softirq);
+ return;
+ }
list_add_tail(&cp->list, head);

/* Trigger the softirq only if the list was previously empty. */

 \ /
  Last update: 2010-05-17 21:07    [W:0.127 / U:14.720 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site