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]
Message-ID: <1322728611.2921.315.camel@twins>
Date:	Thu, 01 Dec 2011 09:36:51 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Venki Pallipadi <venki@...gle.com>,
	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
	Mike Galbraith <efault@....de>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Tim Chen <tim.c.chen@...ux.jf.intel.com>,
	"Shi, Alex" <alex.shi@...el.com>, PaulTurner <pjt@...gle.com>
Subject: Re: [patch 3/6] sched, nohz: sched group, domain aware nohz idle
 load balancing

On Wed, 2011-11-30 at 17:17 -0800, Suresh Siddha wrote:

> So was there any discussion regarding restoring the power savings mode
> at the recent scheduler bof? Even in the latest platforms, there is a
> small power savings when we consolidate the two tasks in two sockets
> onto one socket (though the power difference is shrinking). Turbo
> headroom also plays some role in this. Two tasks in two sockets
> potentially have more turbo headroom compared to the two tasks in one
> socket and thus increased performance with increased power.

Right, so if someone is very keen on it they could try now, but
otherwise it'll come once pjt's got his linsched stuff public and we're
going to do the big topology overhaul.

Anyway, for anybody going to work on it, I think the most important
first step is removing those crazy ass {smt,mc}_power knobs and their
multiple values :-)
--
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