The patch titled
cpuacct: export percpu cpuacct cgroup stats
has been removed from the -mm tree. Its filename was
cpuacct-export-percpu-cpuacct-cgroup-stats.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: cpuacct: export percpu cpuacct cgroup stats
From: Ken Chen <kenchen@xxxxxxxxxx>
Export per-cpu CPU cycle usage for a given cpuacct cgroup. There is a
need for a user space monitor daemon to track group CPU usage on per-cpu
base. It is also useful for monitoring CFS load balancer behavior by
tracking per CPU group usage.
Signed-off-by: Ken Chen <kenchen@xxxxxxxxxx>
Reviewed-by: Li Zefan <lizf@xxxxxxxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxx>
Cc: Paul Menage <menage@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/sched.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff -puN kernel/sched.c~cpuacct-export-percpu-cpuacct-cgroup-stats kernel/sched.c
--- a/kernel/sched.c~cpuacct-export-percpu-cpuacct-cgroup-stats
+++ a/kernel/sched.c
@@ -9458,12 +9458,32 @@ out:
return err;
}
+static int cpuacct_percpu_seq_read(struct cgroup *cgroup, struct cftype *cft,
+ struct seq_file *m)
+{
+ struct cpuacct *ca = cgroup_ca(cgroup);
+ u64 percpu;
+ int i;
+
+ for_each_present_cpu(i) {
+ percpu = cpuacct_cpuusage_read(ca, i);
+ seq_printf(m, "%llu ", (unsigned long long) percpu);
+ }
+ seq_printf(m, "\n");
+ return 0;
+}
+
static struct cftype files[] = {
{
.name = "usage",
.read_u64 = cpuusage_read,
.write_u64 = cpuusage_write,
},
+ {
+ .name = "usage_percpu",
+ .read_seq_string = cpuacct_percpu_seq_read,
+ },
+
};
static int cpuacct_populate(struct cgroup_subsys *ss, struct cgroup *cgrp)
_
Patches currently in -mm which might be from kenchen@xxxxxxxxxx are
origin.patch
linux-next.patch
hugetlb-unsigned-ret-cannot-be-negative.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
