Changes between Version 35 and Version 36 of Developer/SMP


Ignore:
Timestamp:
Feb 18, 2014, 5:13:52 PM (6 years ago)
Author:
Sh
Comment:

/* SMP Locks */ http://git.rtems.org/rtems/commit/?id=0344ce0385fb2ff4f55d4154ae38b438c2168340

Legend:

Unmodified
Added
Removed
Modified
  • Developer/SMP

    v35 v36  
    221221
    222222
    223 The implementation is now CPU architecture specific.
     223SMP locks are implemented as a ticket lock using CPU architecture specific atomic operations.
    224224==  Future Directions  ==
    225225
    226226
    227  *  Use a fair lock on SPARC and x86, e.g. a ticket lock like on ARM and PowerPC.
    228227 *  Use a local context to be able to use scalable lock implementations like the Mellor-Crummey and Scotty (MCS) queue-based locks.
    229228 *  Introduce read-write locks.  Use phase-fair read-write lock implementation.  This can be used for example by the time management code.  The system time may be read frequently, but updates are infrequent.
     
    15771576orthogonal to the blocking states, e.g. DORMANT, SUSPENDED etc.:
    15781577
    1579 ; PROTECTED : The thread is protected from immediate restart, delete and suspend actions. 
     1578; PROTECTED : The thread is protected from immediate restart, delete and suspend actions.  Can be controlled by pthread_setcancelsta