We are expecting runnable_load_avg is less than load.weight, So that runnable_load_avg/load.weight could well present out the system's load distribution.
if not increase the load.weight prior to enqueue_entity_load_avg, it may lead to runnable_load_avg is higher than load.weight, so that people may get confused. Signed-off-by: Lei Wen <[email protected]> Cc: Alex Shi <[email protected]> Cc: Paul Turner <[email protected]> --- kernel/sched/fair.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 2290469..53224d1 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -1778,8 +1778,8 @@ enqueue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags) * Update run-time statistics of the 'current'. */ update_curr(cfs_rq); - enqueue_entity_load_avg(cfs_rq, se, flags & ENQUEUE_WAKEUP); account_entity_enqueue(cfs_rq, se); + enqueue_entity_load_avg(cfs_rq, se, flags & ENQUEUE_WAKEUP); update_cfs_shares(cfs_rq); if (flags & ENQUEUE_WAKEUP) { -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
