I like the idea of higher performance locking and the reduced need for error
checking. We have had internal debates on how much error checking needs to be
done when locking and unlocking a mutex for a shared data structure.
Are these new APIs in addition to the classic RTEMS APIs for similar objects?
Since there are performance benefits, is there any reason to use the classic
API over the self-contained objects?
Finally, the ticket referenced in some of the patches (2843) has a milestone of
6.1. Are the self-contained objects going in 5.1?
Thanks!
Alan
On 12/21/17, 9:19 AM, "devel on behalf of Sebastian Huber"
<devel-boun...@rtems.org on behalf of sebastian.hu...@embedded-brains.de> wrote:
Attached is the generated chapter with references.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
