linux-kernel - Re: [PATCH v7 04/11] sched: adjust exec

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:	Thu, 6 Jun 2013 16:00:12 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Glauber Costa <glommer@...nvz.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Turner <pjt@...gle.com>, linux-kernel@...r.kernel.org,
	cgroups@...r.kernel.org, Frederic Weisbecker <fweisbec@...il.com>,
	devel@...nvz.org, Dave Jones <davej@...hat.com>,
	Ben Hutchings <ben@...adent.org.uk>,
	Lennart Poettering <lennart@...ttering.net>,
	Kay Sievers <kay.sievers@...y.org>
Subject: Re: [PATCH v7 04/11] sched: adjust exec_clock to use it as cpu usage
 metric

On Wed, May 29, 2013 at 03:03:15PM +0400, Glauber Costa wrote:
> exec_clock already provides per-group cpu usage metrics, and can be
> reused by cpuacct in case cpu and cpuacct are comounted.
> 
> However, it is only provided by tasks in fair class. Doing the same for
> rt is easy, and can be done in an already existing hierarchy loop. This
> is an improvement over the independent hierarchy walk executed by
> cpuacct.
> 
> Signed-off-by: Glauber Costa <glommer@...nvz.org>
> CC: Dave Jones <davej@...hat.com>
> CC: Ben Hutchings <ben@...adent.org.uk>
> CC: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> CC: Paul Turner <pjt@...gle.com>
> CC: Lennart Poettering <lennart@...ttering.net>
> CC: Kay Sievers <kay.sievers@...y.org>
> CC: Tejun Heo <tj@...nel.org>

Reviewed-by: Tejun Heo <tj@...nel.org>

Thanks.

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