Daniel,
Which you schedule as the highest priority depends on which task you wish
not to ever be preempted. Of course, the rt- timed tasks will always be
preempted by an ISR. It sounds like you want the 1 millisecond task to
never be preempted, so that one better have the highest priority. I use an
old release of RTL, v0.9J and have had success setting the priorities of
timed tasks.
v/r -
Janet Estabridis
Electrical Engineer
NAWC Code 473E00D
Building 31440 Room 1017
China Lake, CA 93555
[EMAIL PROTECTED]
(760) 939-2896 FAX (760) 939 -3075
> -----Original Message-----
> From: Daniel Krippner [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, July 04, 2000 7:39 AM
> To: [EMAIL PROTECTED]
> Subject: [rtl] preemption
>
>
> Hi everyone!
>
> Question: I got my softplc running now, but when I set up several tasks
> and make one extremely busy, it does not get get preempted by a higher
> priority task;
> I got four tasks, one of which is doing a busy-loop counting up to 60000
> in 10 milliseconds - and a higher priority task that just increments a
> variable each time, which should be scheduled every millisecond. As I
> said, this does not work properly, since the 1 millisecond task seems to
> get called not often enough.
> I set sched_param.sched_priority for all tasks; is that enough or do I
> need to do anything else to get my tasks properly preempted?
>
> thanks
> Daniel
>
> --
> [EMAIL PROTECTED]
> Student of Communication Engineering/Computer Networking
> Furtwangen University of Applied Sciences
> -- [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/
-- [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/
