Maryam Moghaddas wrote:
>
> >
> > The Linux threads package is completely separate to RTLinux, and
> > operates on standard Linux systems with or without RTLinux.
> > If you use the Linux pthreads package then the threads are created as
> > user space processes which can access each others memory.
>
> How about the Linux kernel-threads? Would they beahve the same way?
Kernel threads are subject to the Linux scheduler and consequently can
be locked by kernel activity, and also do not follow pthread API
semantics.
>
> >
> >
> > So I guess it depends on your application, if it requires guaranteed
> > deadlines and/or latencies then it is unlikely that Linux threads will
> > meet the specifications and one of the RT variants should be used, but
> > if your application can withstand missing the occasional deadline, or
> > possibly have exclusive use of the system, then Linux threads may well
> > be acceptable.
> >
>
> My application is a realtime in-memory database. It does not deal with disks. And
>it's
> networking is through the ethernet device driver written for RTLinux OS...
>
> Thanx so much for your complete answers/guidelines...
> maryam
>
Best regards,
Steve
--- [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/
