[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1336147765.6509.41.camel@twins>
Date: Fri, 04 May 2012 18:09:25 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>, mingo@...nel.org,
pjt@...gle.com, efault@....de, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 1/5] sched, fair: Let minimally loaded cpu balance
the group
On Thu, 2012-05-03 at 17:05 -0700, Suresh Siddha wrote:
> On Wed, 2012-05-02 at 16:04 +0530, Srivatsa Vaddagiri wrote:
> > * Peter Zijlstra <a.p.zijlstra@...llo.nl> [2012-05-02 12:31:30]:
> >
> > > > IOW :
> > > >
> > > > balance_load = 0 iff idle_cpu(i) ??
> > >
> > > I think so, even for !0 load_idx, load will only reach zero when we're
> > > idle, just takes longer.
> >
> > Right ...so should we force it to select a idle_cpu by having
> > balance_load = 0 for a idle cpu (ignoring what target_load(i, load_idx)
> > told us as its load?
>
> I think Peter is trying to find the leastly loaded among idle cpu's (in
> other words the longest idle cpu ;)
Nah, Peter isn't trying to do anything smart like that, he's just trying
to pick the least loaded when they're all busy or any idle otherwise.
Afaict the code as it is today is the worst possible choice, always
picking the same (first) will result in that one being the busiest at
all times.
I mean anything will converge (eventually) due to the lower levels
spreading load again, but by pulling to the idlest it should converge
faster.
Picking a random cpu would also work.
--
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