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
| ||
|
Message-ID: <alpine.LFD.2.11.1409111443570.16533@knanqh.ubzr> Date: Thu, 11 Sep 2014 15:17:51 -0400 (EDT) From: Nicolas Pitre <nicolas.pitre@...aro.org> To: Peter Zijlstra <peterz@...radead.org> cc: Vincent Guittot <vincent.guittot@...aro.org>, Ingo Molnar <mingo@...nel.org>, linux-kernel <linux-kernel@...r.kernel.org>, Preeti U Murthy <preeti@...ux.vnet.ibm.com>, Russell King - ARM Linux <linux@....linux.org.uk>, LAK <linux-arm-kernel@...ts.infradead.org>, Rik van Riel <riel@...hat.com>, Morten Rasmussen <Morten.Rasmussen@....com>, Mike Galbraith <efault@....de>, "linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>, Daniel Lezcano <daniel.lezcano@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com> Subject: Re: [PATCH v5 10/12] sched: get CPU's utilization statistic On Thu, 11 Sep 2014, Peter Zijlstra wrote: > On Thu, Sep 11, 2014 at 03:07:52PM +0200, Vincent Guittot wrote: > > > Also I'm not entirely sure I like the usage, utilization names/metrics. > > > I would suggest to reverse them. Call the pure running number > > > 'utilization' and this scaled with capacity 'usage' or so. > > > > ok. i can invert 'usage' and 'utilization', which will give > > > > s/get_cpu_utilization/get_cpu_usage/ > > s/sgs->group_utilization/sgs->group_usage/ > > s/cfs.usage_load_avg/cfs.utilization_load_avg/ > > s/se->avg.usage_avg_contrib/se->avg.utilization_avg_contrib > > s/__update_task_entity_usage/__update_task_entity_utilization > > s/__update_entity_usage_avg_contrib/__update_entity_utilization_avg_contrib > > > > Any other opinions before Vince goes and applies sed on patches? ;-) I don't mind either way, but for sure someone (possibly me) is going to confuse the two soon enough. Please include in the code some formal definition in the context of the scheduler. A comment block right before the corresponding get_cpu_* accessors should be good enough. Nicolas -- 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