Changes between Version 68 and Version 69 of Developer/SMP

Timestamp:

04/18/14 18:18:40 (10 years ago)

Author:

Mayes

Comment:

/* Status of Effort*/

Developer/SMP

@@ -13 +13 @@
 |+
 |-
-|'''Design Issue''' || '''Status Summary''' || '''Notes'''
+|'''Design Issues''' || '''Summary''' || '''Notes'''
 |-
 | [http://www.rtems.org/wiki/index.php/SMP#Low-Level_Start Low Level Start] || TBD || 
@@ -46 +46 @@
 |-
 | [http://www.rtems.org/wiki/index.php/SMP#Semaphores_and_Mutexes Semaphores and Mutexes] || TBD || 
+|-
+|}
+
+
+{| border="1" style="margin: 1em auto 1em auto;text-align: center;"
+|+
+|-
+|'''Implementation Status''' || '''Summary''' || '''Notes'''
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Tool_Chain Tool Chain] || TBD || 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Profiling Profiling] || TBD || 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Interrupt_Support_2 Interrupt Support] || TBD ||
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Clustered_Scheduling_2 Clustered Scheduling] || TBD || 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Multiprocessor_Resource_Sharing_Protocol_-_MrsP  Multiprocessor Resource Sharing Protocol - MrsP] || TBD || 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Fine_Grained_Locking Fine Grained Locking] || TBD || 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Post-Switch_Actions Post-Switch Actions] || TBD || 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Thread_Delete.2FRestart Thread Delete/Restart] || TBD || 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Barrier_Synchronization Barrier Synchronization] || TBD || 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Low-Level_Broadcasts Low-Level Broadcasts] || TBD || 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Termios_Framework Termios Framework] || TBD || 
 |-
 |}
@@ -1482 +1512 @@
 directly which thread is about to block on that mutex.  Some sequences assume
 exactly one executing thread in the system, which is not true on a SMP system
-with more than one processor.  With an SMP lock per mutex object all state
-information for this mutex must be present in the mutex object.  So the locked
-mutex to locked mutex with a waiting thread change must be atomic with respect
-to the mutex SMP lock.  Later mutex timeout or release operations can then get
-the waiting thread and deal with it accordingly.
-=  Implementation  =
-
-
-The blocking operation synchronization state must move from the synchronization
-object (e.g. mutex, message queue) to the thread wait information
-(Thread_Wait_information) since it is clear that the thread has to block and
-not the object.  There may be also multiple threads on different processors
-which queue up on a mutex at the same time.
-
-Blocking threads must be registered in the object under the SMP lock of the
-object and must be independent of the scheduler data structures.  Thus we can
-no longer use the normal chain node of the thread and instead have to add a
-chain node to the thread wait information.
-
-The thread queue operations must no longer use internal locks (e.g. ISR
-disable/enable).  This simplifies them considerable.  The thread queue
-operations must be performed under the SMP lock of the object.  The drawback is
-that the time of disabled interrupts increases. 
+with more than one proce