Hello Gedare,
thanks for your quick review.
On 07/09/16 20:52, Gedare Bloom wrote:
On Tue, Sep 6, 2016 at 8:40 AM, Sebastian Huber
wrote:
Add priority nodes which contribute to the overall thread priority.
The actual priority of a thread is now an aggregation of priority nodes.
The thread pr
On Tue, Sep 6, 2016 at 8:40 AM, Sebastian Huber
wrote:
> Add 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 l
The new thread priority data structures are:
/**
* @brief The priority node to build up a priority aggregation.
*/
typedef struct {
/**
* @brief Node component for a chain or red-black tree.
*/
union {
Chain_Node Chain;
RBTree_Node RBTree;
} Node;
/**
* @brief The prio
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
wrote:
> This patch set reworks the thread pr
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
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 qu