Hi Paul, Ben,
A few queries regarding this patch:
1.What exactly is the significance of introducing sched_avg structure
for a runqueue? If I have
understood correctly, sched_avg keeps track of how long a task has
been active,
how long has it been serviced by the processor and its lifetime.How
does this apply analogously
to the runqueue?
2.Is this a right measure to overwrite rq->load.weight because the
rq->sched_avg does not seem to
take care of task priorities.IOW, what is the idea behind
introducing this metric for the runqueue?
Why cant the run queue load be updated the same way as the cfs_rq
load is updated:
cfs_rq->runnable_load_avg and cfs_rq->blocked_load_avg.
3.What is the significance of passing rq->nr_running in
enqueue_task_fair while updating
the run queue load? Because __update_entity_runnable_avg does not
treat this argument
any differently if it is >1.
Thank you
Regards
Preeti U Murthy
On Thu, Aug 23, 2012 at 7:44 PM, <p...@google.com> wrote:
> From: Ben Segall <bseg...@google.com>
>
> Since runqueues do not have a corresponding sched_entity we instead embed a
> sched_avg structure directly.
>
> Signed-off-by: Ben Segall <bseg...@google.com>
> Reviewed-by: Paul Turner <p...@google.com>
> ---
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
