All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: "Sirotkin, Alexander" <demiurg@ti.com>
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: tasklet latency and system calls on mips
Date: Mon, 18 Aug 2003 10:08:31 -0700	[thread overview]
Message-ID: <20030818100831.A16027@mvista.com> (raw)
In-Reply-To: <3F40F0F0.1080106@ti.com>; from demiurg@ti.com on Mon, Aug 18, 2003 at 06:29:52PM +0300

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

      reply	other threads:[~2003-08-18 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13 13:46 tasklet latency and system calls on mips Sirotkin, Alexander
2003-08-13 16:54 ` Jun Sun
2003-08-14  9:17   ` Sirotkin, Alexander
2003-08-14 16:45     ` Jun Sun
2003-08-18 15:29       ` Sirotkin, Alexander
2003-08-18 17:08         ` Jun Sun [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030818100831.A16027@mvista.com \
    --to=jsun@mvista.com \
    --cc=demiurg@ti.com \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.