[lkml]   [2005]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patches in this message
SubjectDoes smp_reschedule_interrupt really reschedule?
I'm working mostly with Ingo's RT patched kernel, but this may also be a
problem with the vanilla kernel.

Sending out a smp_send_reschedule which causes the
smp_reschedule_interrupt to go off on each CPU. (In Ingo's I was more
concerned with the smp_send_reschedule_allbutself). In
arch/i386/kernel/smp.c there's the following code:

* Reschedule call back. Nothing to do,
* all the work is done automatically when
* we return from the interrupt.
fastcall void smp_reschedule_interrupt(struct pt_regs *regs)

As the comment says, do nothing since all the work is automatically done
at the return from interrupt. But is it? Doesn't the need_resched need
to be set? Here's what I'm seeing with Ingo's kernel. I capture the
time in sched.c when the smp_send_reschedule_allbutself is called, and
also a capture of the time when the schedule actually takes place. I'm
finding differences up to 2 tenths of a second. That's TENTHS! I added
the following patch:

--- arch/i386/kernel/smp.c (revision 181)
+++ arch/i386/kernel/smp.c (working copy)
@@ -593,6 +593,7 @@
trace_special(regs->eip, 0, 0);
+ set_tsk_need_resched(current);

fastcall void smp_call_function_interrupt(struct pt_regs *regs)

(OK the trace_special is from Ingo's patch, but that's what I was
working with)

Now the largest latency between the call smp_send_reschedule and
schedule being called on another CPU is now 200 micro seconds, which is
much more reasonable. But it also shows that a schedule is not taking
place without it.

Now, is there more logic that I'm missing to determine if the schedule
is not needed. With Ingo's patch, he sends this when two RT tasks are
scheduled on the same CPU and one should migrate. But the time this
takes varies tremendously.


-- Steve

Here's the patch for, just in case this is an issue. You just
need to delete the one for Ingo's. And Ingo would need to delete this.
Then again, the above is for a -p0 and this is -p1.

--- a/arch/i386/kernel/smp.c.orig 2005-05-13 14:06:54.000000000 -0400
+++ a/arch/i386/kernel/smp.c 2005-05-13 14:07:28.000000000 -0400
@@ -582,6 +582,7 @@
fastcall void smp_reschedule_interrupt(struct pt_regs *regs)
+ set_tsk_need_resched(current);

fastcall void smp_call_function_interrupt(struct pt_regs *regs)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-05-13 20:21    [W:0.026 / U:8.348 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site