On 25/05/16 03:38, Gedare Bloom wrote:
I guess this means 1 more word of storage per thread queue in the MP
case, and 1 more dereference for each lock context access? It seems
reasonable.
No, there is no additional storage in the thread queue required. The
Thread_queue_Context resides on the stack (similar to the ISR_lock_Context).
On Tue, May 24, 2016 at 8:07 AM, Sebastian Huber
<sebastian.hu...@embedded-brains.de> wrote:
>Drop the multiprocessing (MP) dependent callout parameter from the
>thread queue extract, dequeue, flush and unblock methods. Merge this
>parameter with the lock context into new structure Thread_queue_Context.
>This helps to gets rid of the conditionally compiled method call
>helpers.
--
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
