} On Thu, Oct 12, 2000 at 12:19:26PM -0600, [EMAIL PROTECTED] wrote:
} >
} > > After all, putting a scheduler into an interrupt handler would be
} > > frowned upon by many purist, but this is what is making RTL/RTAI work
} > > for us all right now.
} >
} > A mysterious comment. RTLinux has always worked without the
} > scheduler if it is not neeeded for the applications. And all schedulers
} > for preemptive systems run from interrupt handlers, back since Alan Turing.
} > I don't see how you could do things otherwise, purist or not.
}
}
} I think he was commenting on the fact that the Linux scheduler
} runs from a bottom half instead of an interrupt. A trivial and
} semantic difference, but isn't that what purity is about? =)
The Linux scheduler does run after an interrupt. It gets called on a
ret_from_int on all architectures. This is in the return path of
an interrupt and is in an interrupt even though in_interrupt() doesn't
return true.
-- [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/
