[Top] [All Lists]

Re: tasklet latency and system calls on mips

To: "Sirotkin, Alexander" <>
Subject: Re: tasklet latency and system calls on mips
From: Jun Sun <>
Date: Wed, 13 Aug 2003 09:54:46 -0700
In-reply-to: <>; from on Wed, Aug 13, 2003 at 04:46:04PM +0300
Original-recipient: rfc822;
References: <>
User-agent: Mutt/1.2.5i
On Wed, Aug 13, 2003 at 04:46:04PM +0300, Sirotkin, Alexander wrote:
> Hello dearest all.
> I have a question regarding tasklets on MIPS. I suspect that there is a
> bug in generic MIPS kernel, but I'm not sure yet.
> Linux kernel has a couple of so called "checkpoints" when the system
> should check if there are tasklets to
> run and run them in the following way :
> if (softirq_pending(cpu))
>                     do_softirq();
> One of these places is at the end of interrupt handler (do_IRQ()),
> however this is not the only place. I was under
> impression that this code should be called after system call too. The
> caveat here is that on MIPS (contrary to
> other architectures, such as x86) system call is not an interrupt (it's
> a different exception) and has completely
> different handler. So in x86 it is sufficient to call
> if (softirq_pending(cpu))
>                     do_softirq();
> at the end of do_IRQ because do_IRQ handles system call too, but on MIPS
> it is not. Therefore I believe
> these lines should be added to the end of sys_syscall function on MIPS.
> What do you think ?

softirq/tasklet/bottom_half/etc should only be raised from interrupt
context.  Checking at the end of do_IRQ should be good enough.

One possible mistake in MIPS porting is that if the board uses its private
time interrupt routine poeple may forget to put the above two lines
at the end.  Check against that.

> P.S. The whole issue started when we noticed that user process making
> many system calls has very
> significant impact on device drivers running in tasklet mode 

What kind of impact?  On i386? Or on MIPS?


<Prev in Thread] Current Thread [Next in Thread>