linux-kernel - Re: [PATCH v2 0/11] remove cpu

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] [day] [month] [year] [list]

Date:	Wed, 19 Feb 2014 18:23:34 +0800
From:	Alex Shi <alex.shi@...aro.org>
To:	Vincent Guittot <vincent.guittot@...aro.org>
CC:	Morten Rasmussen <morten.rasmussen@....com>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"peterz@...radead.org" <peterz@...radead.org>,
	"daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>,
	"fweisbec@...il.com" <fweisbec@...il.com>,
	"linux@....linux.org.uk" <linux@....linux.org.uk>,
	"tony.luck@...el.com" <tony.luck@...el.com>,
	"fenghua.yu@...el.com" <fenghua.yu@...el.com>,
	"james.hogan@...tec.com" <james.hogan@...tec.com>,
	"jason.low2@...com" <jason.low2@...com>,
	"viresh.kumar@...aro.org" <viresh.kumar@...aro.org>,
	"hanjun.guo@...aro.org" <hanjun.guo@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"pjt@...gle.com" <pjt@...gle.com>,
	"fengguang.wu@...el.com" <fengguang.wu@...el.com>,
	"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>,
	"wangyun@...ux.vnet.ibm.com" <wangyun@...ux.vnet.ibm.com>
Subject: Re: [PATCH v2 0/11] remove cpu_load in rq


>> Removing cpu_load completely certainly makes things simpler, my worry is
>> just how much was lost by doing it. I agree that cpu_load needs a
>> cleanup, but I can't convince myself that just removing it completely
>> and not having any longer term view of cpu load anymore is without any
>> negative side-effects.
> 
> Hi Alex,
> 
> Have you followed this thread about load_idx and the interest of using
> them to use different average period ?
> https://lkml.org/lkml/2014/1/6/499

Yes, I hoped to use blocked load before. But I still can not figure out
the correct usage of it.
Or maybe we need more quick decay for blocked load?
Or, maybe clean cpu_load is helpful to make room to reconsider this.
> 
> Vincent
> 
>>
>> {source, target}_load() are now instantaneous views of the cpu load,
>> which means that they may change very frequently. That could potentially
>> lead to more task migrations at all levels in the domain hierarchy as we
>> no longer have the more conservative cpu_load[] indexes that were used
>> at NUMA level.
>>
>> Maybe some of the NUMA experts have an opinion about this?
>>
>> In the discussions around V1 I think blocked load came up again as a
>> potential replacement for the current cpu_load array. There are some
>> issues that need to be solved around blocked_load first though.
>>
>> Morten


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