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:	Fri, 04 May 2012 16:55:18 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	Diwakar Tundlam <dtundlam@...dia.com>
Cc:	'Peter Zijlstra' <a.p.zijlstra@...llo.nl>,
	'Ingo Molnar' <mingo@...nel.org>,
	'Andrew Morton' <akpm@...ux-foundation.org>,
	'Christoph Lameter' <cl@...two.org>,
	'Michael Neuling' <mikey@...ling.org>,
	'Stephen Rothwell' <sfr@...b.auug.org.au>,
	'Benjamin Herrenschmidt' <benh@...nel.crashing.org>,
	'David Rientjes' <rientjes@...gle.com>,
	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
	Peter De Schrijver <pdeschrijver@...dia.com>
Subject: RE: [PATCH] sched: Enable arch-specific asym packing option in
 sched domain

On Fri, 2012-05-04 at 16:18 -0700, Diwakar Tundlam wrote:
> Yes, this is for Nvidia's ARM Quad-core Tegra CPU. It is a single package, organized flatly.
> To save power, we want cores to be loaded up in order from cpu0, 1, etc.
> The ASYM_PACKING flag seems to do exactly what we need if set in the domain flag.

Diwakar, But ASYM_PACKING will lead to more task migrations and also it
relies on the periodic load balancing to correct it.

Perhaps we should expose this info more natively and prefer the lower
siblings during task wakeup etc. And perhaps be more aggressive in
moving the load to lower siblings etc.

Can you elaborate more about the power-saving scenario and what causes
the power-savings etc to better understand the problem.

thanks,
suresh




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