On 2013-08-14 17:41, Gedare Bloom wrote:
diff --git a/cpukit/score/include/rtems/score/thread.h 
b/cpukit/score/include/rtems/score/thread.h
>index d346ead..984bc0e 100644
>--- a/cpukit/score/include/rtems/score/thread.h
>+++ b/cpukit/score/include/rtems/score/thread.h
>@@ -378,6 +378,16 @@ struct Thread_Control_struct {
>    bool                                  is_scheduled;
>
>    /**
>+   * @brief This field is true if the thread is in the air.
>+   *
>+   * A thread is in the air if it is in a transient state.  The extract
>+   * operation on a scheduled thread will produce threads in the air.  Such
>+   * threads are no longer on the scheduled chain, but are still allocated to 
a
>+   * processor.  The next enqueue or schedule operation will decide what to 
do.
>+   */
>+  bool                                  is_in_the_air;
>+
At first I did not like this term "in the air" but I cannot think of a
better term right now.


What about "is_transient"?  This state is produced by _Thread_Set_transient().

--
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.
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel

Reply via email to