Hi all,
The driver I've written suffers from interrupt losses. Especially when
there's a lot of activity on the box interrupts are lost.
The handler doesn't do any fancy, it just reads data from the hardware
and puts it in a buffer. Standard read calls read the data from the
buffer and copies it to user space. Since _only_ the handler updates the
write pointer in the buffer and _only_ read updates the read pointer in
the buffer I don't use any protection mechanisms. Read only checks it
doesn't go beond the write pointer and it doesn't use protection for
this because it doesn't matter if it sleeps a bit longer then needed.
My questions:
- Is registering the handler as rt-handler alone sufficent to create a
real time capable handler?
- Do I need to use any rtl specific mechanisms for the buffer?
- Is there a list or particular way to determine wich standard calls are
allowed without losing real time capability. (I ask this because I was a
little confused about the fact one could use inb and friends from within
rt code, because they are macro's)
Thats it for now, probably more later since I'm new to rtl.
Thanks
Greetings Arnaud
-- [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/
