cpuacct.txt 1.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
  1. CPU Accounting Controller
  2. -------------------------
  3. The CPU accounting controller is used to group tasks using cgroups and
  4. account the CPU usage of these groups of tasks.
  5. The CPU accounting controller supports multi-hierarchy groups. An accounting
  6. group accumulates the CPU usage of all of its child groups and the tasks
  7. directly present in its group.
  8. Accounting groups can be created by first mounting the cgroup filesystem.
  9. # mkdir /cgroups
  10. # mount -t cgroup -ocpuacct none /cgroups
  11. With the above step, the initial or the parent accounting group
  12. becomes visible at /cgroups. At bootup, this group includes all the
  13. tasks in the system. /cgroups/tasks lists the tasks in this cgroup.
  14. /cgroups/cpuacct.usage gives the CPU time (in nanoseconds) obtained by
  15. this group which is essentially the CPU time obtained by all the tasks
  16. in the system.
  17. New accounting groups can be created under the parent group /cgroups.
  18. # cd /cgroups
  19. # mkdir g1
  20. # echo $$ > g1
  21. The above steps create a new group g1 and move the current shell
  22. process (bash) into it. CPU time consumed by this bash and its children
  23. can be obtained from g1/cpuacct.usage and the same is accumulated in
  24. /cgroups/cpuacct.usage also.
  25. cpuacct.stat file lists a few statistics which further divide the
  26. CPU time obtained by the cgroup into user and system times. Currently
  27. the following statistics are supported:
  28. user: Time spent by tasks of the cgroup in user mode.
  29. system: Time spent by tasks of the cgroup in kernel mode.
  30. user and system are in USER_HZ unit.
  31. cpuacct controller uses percpu_counter interface to collect user and
  32. system times. This has two side effects:
  33. - It is theoretically possible to see wrong values for user and system times.
  34. This is because percpu_counter_read() on 32bit systems isn't safe
  35. against concurrent writes.
  36. - It is possible to see slightly outdated values for user and system times
  37. due to the batch processing nature of percpu_counter.