[EMAIL PROTECTED] wrote:
> Process A is the highest priority
> Process B is lowest realtime priority
> Process A reads from the device driver
> Process B runs because A is blocked
> Interrupt fires, schedules tasklet to read data on behalf of process
> Process B runs again because no reschedule occurred <- Priority
> Inversion Timer interrupt fires
> Ksoftirqd runs tasklet Tasklet wakes up Process A <- Priority
> Inversion ends
> Process A runs <- No Priority inversion here
>
More confusion... In this situation, doesn't ksoftirqd run after the
hardware interrupt exits? If so, I would have no concerns at all about
priority inversion using tasklets.
-Michael
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the FAQ at http://kernelnewbies.org/FAQ
