[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPM31RLKvmRr_76B12zTnqh6+htm++hmSiM9O3EsuRd47oFtpw@mail.gmail.com>
Date: Fri, 17 Feb 2012 02:54:55 -0800
From: Paul Turner <pjt@...gle.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: linux-kernel@...r.kernel.org, Venki Pallipadi <venki@...gle.com>,
Srivatsa Vaddagiri <vatsa@...ibm.com>,
Mike Galbraith <efault@....de>,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
Ben Segall <bsegall@...gle.com>, Ingo Molnar <mingo@...e.hu>,
Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>
Subject: Re: [RFC PATCH 14/14] sched: implement usage tracking
On Thu, Feb 16, 2012 at 5:37 AM, Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> On Wed, 2012-02-01 at 17:38 -0800, Paul Turner wrote:
>> static inline void update_rq_runnable_avg(struct rq *rq, int runnable)
>> {
>> - __update_entity_runnable_avg(rq->clock_task, &rq->avg, runnable);
>> + __update_entity_runnable_avg(rq->clock_task, &rq->avg, runnable,
>> + runnable);
>
> Its not immediately obvious why we use @runnable for @running,
Isn't it? An rq is the root of all scheduling -- if there are any
runnable tasks than one of them better be running when this is called.
I can add a comment to this effect.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists