On Mon, Sep 24, 2012 at 1:39 PM, Benjamin Segall wrote:
> blocked_load_avg ~= \sum_child
> child.runnable_avg_sum/child.runnable_avg_period * child.weight
>
> The thought was: So if all the children have hit zero runnable_avg_sum
> (or in the case of a child task, will when they wake up), then
>
On Mon, Sep 24, 2012 at 1:39 PM, Benjamin Segall bseg...@google.com wrote:
blocked_load_avg ~= \sum_child
child.runnable_avg_sum/child.runnable_avg_period * child.weight
The thought was: So if all the children have hit zero runnable_avg_sum
(or in the case of a child task, will when they
blocked_load_avg ~= \sum_child child.runnable_avg_sum/child.runnable_avg_period
* child.weight
The thought was: So if all the children have hit zero runnable_avg_sum
(or in the case of a child task, will when they wake up), then
blocked_avg sum should also hit zero at the same and we're in
Am 23.08.2012 16:14, schrieb p...@google.com:
> From: Paul Turner
>
> Now that the machinery in place is in place to compute contributed load in a
> bottom up fashion; replace the shares distribution code within update_shares()
> accordingly.
[snip]
> static int update_shares_cpu(struct
Am 23.08.2012 16:14, schrieb p...@google.com:
From: Paul Turner p...@google.com
Now that the machinery in place is in place to compute contributed load in a
bottom up fashion; replace the shares distribution code within update_shares()
accordingly.
[snip]
static int
blocked_load_avg ~= \sum_child child.runnable_avg_sum/child.runnable_avg_period
* child.weight
The thought was: So if all the children have hit zero runnable_avg_sum
(or in the case of a child task, will when they wake up), then
blocked_avg sum should also hit zero at the same and we're in
From: Paul Turner
Now that the machinery in place is in place to compute contributed load in a
bottom up fashion; replace the shares distribution code within update_shares()
accordingly.
Signed-off-by: Paul Turner
Reviewed-by: Ben Segall
---
kernel/sched/debug.c |8 ---
From: Paul Turner p...@google.com
Now that the machinery in place is in place to compute contributed load in a
bottom up fashion; replace the shares distribution code within update_shares()
accordingly.
Signed-off-by: Paul Turner p...@google.com
Reviewed-by: Ben Segall bseg...@google.com
---
8 matches
Mail list logo
