Dear All,

so far I am running all my application in one-shot mode. Since all
periodic tasks are running at multiples of 0.1 ms, I thought I go to try
to run them in periodic mode, because it does increase scheduling
precision, as I understand it.

Now this application consists of several modules, most of which do
contain periodic tasks. Some of these are loaded/unloaded several times
during the "lifetime" of the longer lived modules.
Skimming through the sources, I think I need to provide starting times
that are all on times 
  (return value of rtl_set_periodic_mode) * n * period
Is this correct ?

How do you synchronize modules in this regard ? If I use my main module
(one that is active all time) to set up the periodic mode, how would I
send the the start-value to a newly loaded module ? Do I need rt_ipc for
that or is there an easier solution ?

Now that I have the timer start-time, how do I determine the task
start-time ? Is it ok to add the period to the timer start-time until its
bigger than rt_get_time ?

Btw: If it makes a difference: this is with RT-Linux v1.

-- Jochen
 Heinrich-Heine-Universit�t D�sseldorf          [EMAIL PROTECTED]
 Institut f�r Physikalische Chemie I               phone ++49-211-8113681
 Universit�tsstr. 26.43.02.29                      fax   ++49-211-8115195
 40225 D�sseldorf, Germany       www-public.rz.uni-duesseldorf.de/~jochen
--- [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/

Reply via email to