On Wed, Jan 05, 2000 at 09:03:50AM -0700, Philip N Daly wrote:
> Good to see progress on the API issue. Steve Papacharalambous is right
> about using the pthread nomenclature with noo-POSIX APIS being a bad idea.
>
> The only contribution I wish to make is one about context: as I recall
> from Vienna there is a distinct difference between the RTAI task creation
> routine and the RTL one. The difference, and correct me if I'm wrong,
> is that the RTL one *must* be called in the init_module whereas the
> RTAI one can be called anywhere. I prefer the latter as it is quite
> common for users to setup a fifo handling incoming (user) commands
> to stop/start/reset tasks etc. I want to know that the code can be used
> whereever I like.
RTLinux requires task creation in _Linux mode_ but does not allow it
in RT mode (during the execution of an RT task or interrupt handler).
Tasks can be created by fifo handlers since they run in Linux mode.
Tasks cannot be created during RT mode because we do not have dynamic memory
allocation. However, it would be easy to construct a scheduler that
pre-allocated RTL_MAX_TASKS threads at startup and then allocated from
this list.
Or without making a new scheduler, it is easy to create a number of
tasks at startup and have them wait for something to do in suspended mode.
--- [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/