linux-kernel - Re: [RFCv3 PATCH 36/48] sched: Count number of shallower idle-states in struct sched_group

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: <20150324131439.GO23123@twins.programming.kicks-ass.net>
Date:	Tue, 24 Mar 2015 14:14:39 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Morten Rasmussen <morten.rasmussen@....com>
Cc:	mingo@...hat.com, vincent.guittot@...aro.org,
	dietmar.eggemann@....com, yuyang.du@...el.com,
	preeti@...ux.vnet.ibm.com, mturquette@...aro.org, nico@...aro.org,
	rjw@...ysocki.net, juri.lelli@....com, linux-kernel@...r.kernel.org
Subject: Re: [RFCv3 PATCH 36/48] sched: Count number of shallower idle-states
 in struct sched_group_energy

On Wed, Feb 04, 2015 at 06:31:13PM +0000, Morten Rasmussen wrote:
> cpuidle associates all idle-states with each cpu while the energy model
> associates them with the sched_group covering the cpus coordinating
> entry to the idle-state. To get idle-state power consumption it is
> therefore necessary to translate from cpuidle idle-state index to energy
> model index. For this purpose it is helpful to know how many idle-states
> that are listed in lower level sched_groups (in struct
> sched_group_energy).

I think this could use some text to describe how that number is useful.

I suspect is has something to do with bigger domains having more idle
modes (package C states etc..).
--
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/