Can coexists rtems tasks (Classic API) and posix task??

[Nicolás Alvarez]

Great, thanks for the answers.

*Ing. Nicolás Alvarez*
*
*
cel: 03548-15638454
http://ar.linkedin.com/in/ingalvarez/en


On Fri, Aug 30, 2013 at 6:06 PM, Joel Sherrill <Joel.Sherrill at oarcorp.com>wrote:

> Gedare is not mistaken. Classic tasks can make POSIX thread calls and vice
> versa.
>
> Beware the pthreads are defined to exit silently deleting themselves and
> classic tasks consider this a fatal error.
>
> Gedare Bloom <gedare at rtems.org> wrote:
>
>
> Also note that you would need to "configure" your application
> correctly so that the resources are available to create tasks of both
> types, e.g.
> #define CONFIGURE_MAXIMUM_TASKS 2
> #define CONFIGURE_MAXIMUM_POSIX_THREADS 3
>
> if you have 2 classic tasks and 3 pthreads.
>
> On Fri, Aug 30, 2013 at 4:22 PM, Gedare Bloom <gedare at rtems.org> wrote:
> > Yes. If I'm not mistaken, RTEMS tasks can also make posix calls.
> >
> > Posix thread priorities are mapped to the RTEMS internal priority
> > range of 0-255 (realistically, 1-254, since 0 and 255 are reserved).
> > Note that the pthread priorties are inverted, so a 1 becomes 254, the
> > lowest schedulable priority in the system. After the mapping, the
> > scheduler sees both types of tasks as the same. You can inspect how
> > this is done when a pthread is created in the
> > cpukit/posix/src/pthreadcreate.c.
> >
> > -Gedare
> >
> >
> >
> > On Fri, Aug 30, 2013 at 3:13 PM, Nicolás Alvarez <nicoalar.22 at gmail.com>
> wrote:
> >> Hi all,
> >>
> >> It is possible to use in one app both kind of task? What is the
> scheduler
> >> behavior?
> >>
> >> Regards,
> >>
> >> Ing. Nicolás Alvarez
> >>
> >>
> >> _______________________________________________
> >> rtems-users mailing list
> >> rtems-users at rtems.org
> >> http://www.rtems.org/mailman/listinfo/rtems-users
> >>
>
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20130830/32dad121/attachment-0001.html>