Re: Tasklet usage?

[Robert Hancock]

I recently made a similar change for what sounds like a similar piece of 
hardware (though in our case it was filling a FIFO for output purposes, 
which cannot be allowed to run empty, when we receive a FIFO-almost-empty 
interrupt from the device).

The tasklet will not necessarily get run immediately, as other tasklets may 
be pending on that CPU. You should be able to reduce the likelihood of this 
happening by using tasklet_hi_schedule instead of tasklet_schedule, that 
should put it ahead of any network, SCSI, etc. tasklets that may be pending.

Tasklets can only get interrupted by hard interrupts (which as someone 
mentioned, is pretty much the point of them).

As far as rescheduling the tasklet, I believe if the tasklet hasn't started, 
it will only execute once regardless of how many times you call 
tasklet_schedule. If it has already started running, and the tasklet gets 
scheduled, it will run again once it finishes.

Locking-wise, for any critical regions shared between the hard IRQ handler 
and either the tasklet or user context, spin_lock_irqsave is what you need. 
However, critical regions shared only between user context and the tasklet 
can use spin_lock_bh instead (which disables only bottom-halves and 
tasklets, not interrupts).


----- Original Message ----- 
From: "Pierre Ossman" <drzeus-list@xxxxxxxxx>
Newsgroups: fa.linux.kernel
To: "LKML" <linux-kernel@xxxxxxxxxxxxxxx>
Sent: Friday, October 15, 2004 7:15 AM
Subject: Tasklet usage?


> My driver needs to spend a lot of time inside the interrupt handler 
> (draining a FIFO). I suspect this might cause problems blocking other 
> interrupt handlers so I was thinking about moving this into a tasklet.
> Not being to familiar with tasklets, a few questions pop up.
>
> * Will a tasklet scheduled from the interrupt handler be executed as soon 
> as interrupt handling is done?
> * Can tasklets be preempted?
> * If a tasklet gets scheduled while running, will it be executed once 
> more? (Needed if I get another FIFO interrupt while the tasklet is just 
> exiting).
>
> The FIFO is a bit small so time is of the essence. That's why this routine 
> is in the interrupt handler to begin with.
>
> Rgds
> Pierre Ossman
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/ 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/