lkml.org 
[lkml]   [2008]   [Nov]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Add hierarchical accounting to cpu accounting controller
On Tue, 4 Nov 2008 18:19:37 +0530 Bharata B Rao wrote:

> Add hierarchical accounting to cpu accounting controller and cpuacct
> documentation.
>
> Currently, while charging the task's cputime to its accounting group,
> the accounting group hierarchy isn't updated. This patch charges the cputime
> of a task to its accounting group and all its parent accounting groups.
>
> Reported-by: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
> Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> CC: Peter Zijlstra <a.p.zijlstra@chello.nl>
> CC: Ingo Molnar <mingo@elte.hu>
> CC: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
> Reviewed-by: Paul Menage <menage@google.com>
> ---
> Documentation/controllers/cpuacct.txt | 32 ++++++++++++++++++++++++++++++++
> kernel/sched.c | 10 ++++++++--
> 2 files changed, 40 insertions(+), 2 deletions(-)
>
> --- /dev/null
> +++ b/Documentation/controllers/cpuacct.txt
> @@ -0,0 +1,32 @@
> +CPU Accounting Controller
> +-------------------------
> +
> +The CPU accounting controller is used to group tasks using cgroups and
> +account the CPU usage of these group of tasks.
> +
> +The CPU accounting controller supports multi-hierarchy groups. An accounting
> +group accumulates the CPU usage of all of it's child groups and

its {it's means "it is"}

> +the tasks directly present in it's group.

its

> +
> +Accounting groups can be created by first mounting the cgroup filesystem.
> +
> +# mkdir /cgroups
> +# mount -t cgroup -ocpuacct none /cgroups
> +
> +With the above step, the initial or the parent accounting group
> +becomes visible at /cgroups. At bootup, this group comprises of all the

"comprises of all" seems awkward to me. Maybe "includes all" or
"comprises all" if you have to use that word. ;)

> +tasks in the system. /cgroups/tasks lists the tasks in this cgroup.
> +/cgroups/cpuacct.usage gives the CPU time (in nanoseconds) obtained by
> +this group which is essentially the CPU time obtained by all the tasks
> +in the system.
> +
> +New accounting groups can be created under the parent group /cgroups.
> +
> +# cd /cgroups
> +# mkdir g1
> +# echo $$ > g1
> +
> +The above steps create a new group g1 and move the current shell
> +process (bash) into it. CPU time consumed by this bash and it's children

its

> +can be obtained from g1/cpuacct.usage and the same gets accumulated in

is accumulated in

> +/cgroups/cpuacct.usage also.



> Performance numbers
> ==================
> 2x2HT=4CPU i386 running 2.6.28-rc3
>
> All benchmarks were run from bash which belonged to the grand

grandchild (?)
Otherwise it says that the "child group" is "grand."
Oh, never mind. I thought that this was part of a doc file, but it's not.


> child group of the topmost accounting group. The tests were
> first run on 2628rc3 and then on 2628rc3+this patch and the
> normalized difference between the two runs is shown below.
>
> I. hackbench
> ============
> # ./hackbench 100 process 100
> Running with 100*40 (== 4000) tasks.
> Normalized time difference for avg of 5 runs: 1.0059
>
> # ./hackbench 25 thread 100
> Running with 25*40 (== 1000) tasks.
> Normalized time difference for avg of 5 runs: 1.0139
>
> II. lmbench
> ===========
> ---------------------
> 4 threads
> ---------------------
> size Normalized
> (kb) Change (Time)
> ---------------------
> 16 1.1017
> 64 1.1168
> 128 1.1072
> 256 1.0085
> --------------------
> 8 threads
> -------------------
> 16 1.1835
> 64 1.0617
> 128 0.9980
> 256 0.9682
> -------------------
> 16 threads
> -------------------
> 16 1.1186
> 64 0.9921
> 128 0.9505
> 256 1.0043
> -------------------
> 32 threads
> -------------------
> 16 1.0005
> 64 1.0089
> 128 1.0019
> 256 1.0226
> -------------------
> 64 threads
> -------------------
> 16 1.0207
> 64 1.0385
> 128 1.0109
> 256 1.0159
> -------------------
>
> III. volanomark
> ===============
> Normalized average throughput difference for loopback test
>
> ------------------------------------------------------------
> Nr runs Normalized average throughput difference
> ------------------------------------------------------------
> 10 0.9579
> ------------------------------------------------------------
> 4 1.1465
> ------------------------------------------------------------
> 9 0.9451
> ------------------------------------------------------------
> 19 1.0133
> ------------------------------------------------------------
> --


---
~Randy


\
 
 \ /
  Last update: 2008-11-04 18:23    [W:0.107 / U:0.408 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site