Hi RTLinux list,
I'm new to real-time Linux, so this question may seem a little simple.
I'm implementing a machine controller on a dedicated system and I'd like to
see if I could do it on a more general system with RTLinux. The system has a
sample rate of 10kHz and is currently implemented on a couple of TMS320C40s.
I have read a fair amount of the literature on RTLinux available on the web
site and it seems to me that the major problem with using RTLinux would be its
interrupt latency. From the literature it seems that the worst case interrupt
latency can be as high as 15 to 20 us - this is a large amount of the
available 100 us and would be a major problem.
I would imagine that this interrupt latency is solely caused by the amount of
time required to switch contexts - i.e. push all the registers etc.
So the question is - Is this large latency due to the structure of context
switching programmed into the interrupt executive within RTLinux, or is it due
to the structure of the hardware - i.e. the amount of x86 instructions
required.
If the later, would the interrupt latency be improved by using other hardware,
namely MIPS or ARM processors (two processors I'm considering for real-time
applications which have Linux ports)?
--
Andrew Tuckey
Postdoctoral Research Scientist
Eindhoven University of Technology
EE Dept., Group EMV, Room EL 1.13
PO Box 513 Phone: +31 - 40 2 47 3895
5600 MB EINDHOVEN Fax: +31 - 40 2 43 4364
The Netherlands Email: [EMAIL PROTECTED]
-- [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/
