On Tue, Dec 19, 2000 at 08:25:57PM +0800, dyd wrote:
> Dear Yodaiken,
>
> I've remove the bug in my keyboard irq.
>
> When a key is typed , a rt thread which is blocking waiting for the key
> should be wakeup. The wakeup should be done by first changing the thread
> state to RTL_THREAD_READY then calling rtl_schedule or rtl_reschedule.
>
> I forgot to call rtl_schedule. I made this mistake because I've assumed that
> schedule will be done when irq returned. This is the way Linux do.
>
> So the question is that if it is reasonable to let rtlinux do rtl_schedule
> when it returned from a realtime interrupt?
Not reasonable because it's not always the case that a schedule makes sense
after an interrupt and we don't want to force the overhead. For example,
suppose you are collecting data at a very high interrupt rate and run a thread
every millisecond to consume the data -- you don't want a resched after each
interrupt.
>
>
> Thanks
>
> Regards
> Dyd
>
>
>
>
>
--
---------------------------------------------------------
Victor Yodaiken
Finite State Machine Labs: The RTLinux Company.
www.fsmlabs.com www.rtlinux.com
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
