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:	Wed, 20 Feb 2013 22:08:52 +0800
From:	Alex Shi <alex.shi@...el.com>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	torvalds@...ux-foundation.org, mingo@...hat.com,
	tglx@...utronix.de, akpm@...ux-foundation.org,
	arjan@...ux.intel.com, bp@...en8.de, pjt@...gle.com,
	namhyung@...nel.org, efault@....de, vincent.guittot@...aro.org,
	gregkh@...uxfoundation.org, preeti@...ux.vnet.ibm.com,
	viresh.kumar@...aro.org, linux-kernel@...r.kernel.org,
	morten.rasmussen@....com
Subject: Re: [patch v5 11/15] sched: add power/performance balance allow flag


>>> (power_lb == 1 && perf_lb == 1) is incorrect and impossible to have.
>>>
>>> (power_lb == 0 && perf_lb == 0) is possible and it means there is no any
>>> balance on this cpu.
>>>
>>> So, enumeration is not enough.
>>
>> Huh.. both 0 doesn't make any sense either. If there's no balancing, we
>> shouldn't be here to begin with.
> 
> Also, why is this in the lb_env at all, shouldn't we simply use the
> global sched_balance_policy all over the place? Its not like we want to
> change power/perf on a finer granularity.

they are in lb_env, since we need to set them according to each group
status, mostly in update_sd_lb_power_stats().

Even the sched_balance_policy is powersaving, the domain may also need
performance balance since there are maybe too much tasks or much
imbalance in domain.

when we find the domain is not suitable for power balance, we will set
lb_perf = 1, then we don't need go through other groups for power info
collection.
> 


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ