[RTEMS Project] #2556: Implement the O(m) Independence-Preserving Protocol (OMIP)

RTEMS trac trac at rtems.org
Wed Jun 22 12:48:46 UTC 2016

#2556: Implement the O(m) Independence-Preserving Protocol (OMIP)
 Reporter:  sebastian.huber  |       Owner:  sebastian.huber
     Type:  enhancement      |      Status:  accepted
 Priority:  normal           |   Milestone:  4.12
Component:  cpukit           |     Version:  4.12
 Severity:  normal           |  Resolution:
 Keywords:                   |

Comment (by Sebastian Huber <sebastian.huber@…>):

 In [changeset:"9bfad8cd519f17cbb26a672868169fcd304d5bd5/rtems"]:
 #!CommitTicketReference repository="rtems"
 score: Add thread priority to scheduler nodes

 The thread priority is manifest in two independent areas.  One area is
 the user visible thread priority along with a potential thread queue.
 The other is the scheduler.  Currently, a thread priority update via
 _Thread_Change_priority() first updates the user visble thread priority
 and the thread queue, then the scheduler is notified if necessary.  The
 priority is passed to the scheduler via a local variable.  A generation
 counter ensures that the scheduler discards out-of-date priorities.

 This use of a local variable ties the update in these two areas close
 together.  For later enhancements and the OMIP locking protocol
 implementation we need more flexibility.  Add a thread priority
 information block to Scheduler_Node and synchronize priority value
 updates via a sequence lock on SMP configurations.

 Update #2556.

Ticket URL: <http://devel.rtems.org/ticket/2556#comment:9>
RTEMS Project <http://www.rtems.org/>
RTEMS Project

More information about the bugs mailing list