I will try to read this code, but probably not until Friday. One question from the high-level description, can you clarify what "aggregation" means? Maybe this comes clear in one of the patches.
Gedare On Tue, Sep 6, 2016 at 8:40 AM, Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote: > This patch set reworks the thread priority management. The main goals are > > 1. an enhanced implementation of the priority inheritance protocol, and > > 2. support for the OMIP locking protocol. > > Instead of the current and real priority values in combination with the > resource count use thread priority nodes which contribute to the overall > thread > priority. > > The actual priority of a thread is now an aggregation of priority nodes. > The thread priority aggregation for the home scheduler instance of a > thread consists of at least one priority node, which is normally the > real priority of the thread. The locking protocols (e.g. priority > ceiling and priority inheritance), rate-monotonic period objects and the > POSIX sporadic server add, change and remove priority nodes. > > A thread changes its priority now immediately, e.g. priority changes are > not deferred until the thread releases its last resource. > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
