Hi, If you profile the scheduler and know it's maximum run time then you could put in some logic where you set the period to prevent the user from setting it to short. You could have it default to a minimum value and send a message via fifo to the user. Or you could just ignore the change in period if it is out of bounds.
Rich -----Original Message----- From: Murillo-Garcia Raul [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 16, 2002 7:00 AM To: [EMAIL PROTECTED] Subject: [rtl] thread overrun Hi there I apologise if this question has already been posted but I'm new in this list. I have an application that supports multiple real-time threads that run at rates specified by the user. If these rates are very large the computer crashes. My hypothesis is that a thread is invoked before it is finished since the execution time is larger that the thread period. Is there any mechanism to prevent this from happening. I tried with a watchdog thread with the highest priority but it didn't seem to work. many thanks in advance -- [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/ -- [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/
