From: Li Zefan <lizf@cn.fujitsu.com>
To: Ken Chen <kenchen@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch] export percpu cpuacct cgroup stats
Date: Thu, 04 Dec 2008 13:34:27 +0800 [thread overview]
Message-ID: <49376BE3.1040909@cn.fujitsu.com> (raw)
In-Reply-To: <b040c32a0812032048x4a11dc26k184a4b279b509050@mail.gmail.com>
(I guess it's more appropriate to ask Ingo to pick up this patch)
Ken Chen wrote:
> This patch 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 monitor CFS load
> balancer behavior by tracking per CPU group usage.
>
>
> Signed-off-by: Ken Chen <kenchen@google.com>
>
> diff --git a/kernel/sched.c b/kernel/sched.c
> index b7480fb..cd78948 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -9345,12 +9345,34 @@ 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_possible_cpu(i) {
> + spin_lock_irq(&cpu_rq(i)->lock);
> + percpu = *percpu_ptr(ca->cpuusage, i);
> + spin_unlock_irq(&cpu_rq(i)->lock);
> + seq_printf(m, "%lld ", percpu);
Should be %llu. And if we don't cast percpu to unsigned long long, will it trigger
compile warning in some archs?
> + }
> + seq_printf(m, "\n");
> + return 0;
> +}
> +
> static struct cftype files[] = {
> {
> .name = "usage",
> .read_u64 = cpuusage_read,
> .write_u64 = cpuusage_write,
> },
> + {
> + .name = "percpu",
IMO percpu_usage is a better name.
> + .read_seq_string = cpuacct_percpu_seq_read,
> + },
> +
> };
>
next prev parent reply other threads:[~2008-12-04 5:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 4:48 [patch] export percpu cpuacct cgroup stats Ken Chen
2008-12-04 5:34 ` Li Zefan [this message]
2008-12-04 9:24 ` Ingo Molnar
2008-12-04 23:02 ` Paul Menage
2008-12-05 7:44 ` Ken Chen
2008-12-05 7:54 ` Li Zefan
2008-12-05 8:30 ` Ken Chen
2008-12-05 8:35 ` Li Zefan
2008-12-05 13:52 ` Ingo Molnar
2008-12-05 18:16 ` Ken Chen
2008-12-07 7:27 ` Andrew Morton
2008-12-08 14:33 ` Ingo Molnar
2008-12-05 18:10 ` Ken Chen
2008-12-08 1:25 ` Li Zefan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49376BE3.1040909@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox