linux-kernel - Re: [RFC PATCH 0/2] sched: simplify the select_task_rq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 24 Jan 2013 11:34:26 +0100
From:	Mike Galbraith <bitbucket@...ine.de>
To:	Michael Wang <wangyun@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...hat.com,
	peterz@...radead.org, mingo@...nel.org, a.p.zijlstra@...llo.nl
Subject: Re: [RFC PATCH 0/2] sched: simplify the select_task_rq_fair()

On Thu, 2013-01-24 at 17:26 +0800, Michael Wang wrote: 
> On 01/24/2013 05:07 PM, Mike Galbraith wrote:
> > On Thu, 2013-01-24 at 16:14 +0800, Michael Wang wrote:
> > 
> >> Now it's time to work on v3 I think, let's see what we could get this time.
> > 
> > Maybe v3 can try to not waste so much ram on affine map?
> 
> Yeah, that has been a question in my mind at very beginning, but how...

Allocate at domain build time the max we can acquire via hotplug?
> > Even better would be if it could just go away, along with relic of the
> > bad old days wake_affine(), and we make the balance path so damn light
> > but clever that select_idle_sibling() can go away too... and a pony ;-)
> 
> Hmm...may be, I need some consideration here, a totally balance path,
> interesting...

Unification is the right target, hitting it might not be so easy though.

> But I think we still need the clean code which sbm bring to us, do we?

Sure, if it makes things perform better.

-Mike

--
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/