linux-mips
[Top] [All Lists]

Re: tasklet latency and system calls on mips

To: "Sirotkin, Alexander" <demiurg@ti.com>
Subject: Re: tasklet latency and system calls on mips
From: Jun Sun <jsun@mvista.com>
Date: Mon, 18 Aug 2003 10:08:31 -0700
Cc: linux-mips@linux-mips.org, jsun@mvista.com
In-reply-to: <3F40F0F0.1080106@ti.com>; from demiurg@ti.com on Mon, Aug 18, 2003 at 06:29:52PM +0300
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <3F3A411C.70603@ti.com> <20030813095446.C9655@mvista.com> <3F3B53C0.30408@ti.com> <20030814094515.B1203@mvista.com> <3F40F0F0.1080106@ti.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.2.5i
On Mon, Aug 18, 2003 at 06:29:52PM +0300, Sirotkin, Alexander wrote:
> 
> 
> 
> The tasklet should be executed at the return of interrupt handling.
> 
> If not, there is a bug.
> 
>   
> 
> I have a feeling that we are going in circles. Tasklets are executed at
> the return of interrupt handler.
> However, I suspect that this is not enough. 

If you follow this, plus "tasklet_schedule() is indeed called in an interrupt
handler", you will should see "executing tasklet at the return of interrupt
handler"  is _obviously_ enough.

> On mips (contrary to x86),
> system call is NOT an interrupt.
> It's a different exception with different handler. Therefore I suspect
> that tasklets are NOT called at 
> the end of system call exception handler (which is a different handler,
> not do_IRQ).
>

... which is fine, if you can follow the above logic.

Jun

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