Re: [PATCH v2 2/4] sched/fair: add util_est on top of PELT

[Patrick Bellasi]

On 13-Dec 17:05, Peter Zijlstra wrote:
> On Tue, Dec 05, 2017 at 05:10:16PM +0000, Patrick Bellasi wrote:
> > +	if (cfs_rq->nr_running > 0) {
> > +		util_est  = cfs_rq->util_est_runnable;
> > +		util_est -= task_util_est(p);
> > +		if (util_est < 0)
> > +			util_est = 0;
> > +		cfs_rq->util_est_runnable = util_est;
> > +	} else {
> 
> I'm thinking that's an explicit load-store to avoid intermediate values
> landing in cfs_rq->util_esp_runnable, right?

Was mainly to have an unsigned util_est for the following "sub"...


> That would need READ_ONCE() / WRITE_ONCE() I think, without that the
> compiler is free to munge the lot together.

... do we still need the {READ,WRITE}_ONCE() in this case?
I guess adding them however does not hurts.

Steering back at that code however it can likely by optimized to avoid
the else branch... will update and add the barriers.

Cheers Patrick.

-- 
#include <best/regards.h>

Patrick Bellasi