From: Glauber Costa <glommer@parallels.com>
To: linux-kernel@vger.kernel.org
Cc: paul@paulmenage.org, lizf@cn.fujitsu.com, daniel.lezcano@free.fr,
a.p.zijlstra@chello.nl, jbottomley@parallels.com, pjt@google.com,
cgroups@vger.kernel.org, bsingharora@gmail.com, devel@openvz.org,
kamezawa.hiroyu@jp.fujitsu.com
Subject: [PATCH v2 0/3] cpuacct cgroup refactoring
Date: Mon, 28 Nov 2011 14:45:16 -0200 [thread overview]
Message-ID: <1322498719-2255-1-git-send-email-glommer@parallels.com> (raw)
Hi,
This is the same series I've already sent before. Just sending again
after the conflict with the code that was in tip.git
Best regards,
Glauber Costa (3):
Change cpustat fields to an array.
Reuse cgroup's parent pointer
cpuacct.stat: re-use scheduler statistics for the root cgroup
arch/s390/appldata/appldata_os.c | 16 +-
arch/x86/include/asm/i387.h | 2 +-
drivers/cpufreq/cpufreq_conservative.c | 38 +++---
drivers/cpufreq/cpufreq_ondemand.c | 38 +++---
drivers/macintosh/rack-meter.c | 8 +-
fs/proc/stat.c | 63 ++++-----
fs/proc/uptime.c | 4 +-
include/linux/kernel_stat.h | 36 +++--
kernel/sched/core.c | 242 +++++++++++++++----------------
kernel/sched/sched.h | 33 ++++-
10 files changed, 248 insertions(+), 232 deletions(-)
--
1.7.6.4
next reply other threads:[~2011-11-28 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 16:45 Glauber Costa [this message]
2011-11-28 16:45 ` [PATCH v2 1/3] Change cpustat fields to an array Glauber Costa
2011-12-06 9:56 ` [tip:sched/core] sched/accounting: " tip-bot for Glauber Costa
2011-11-28 16:45 ` [PATCH v2 2/3] Reuse cgroup's parent pointer Glauber Costa
2011-12-06 9:57 ` [tip:sched/core] sched/accounting, cgroups: " tip-bot for Glauber Costa
2011-11-28 16:45 ` [PATCH v2 3/3] cpuacct.stat: re-use scheduler statistics for the root cgroup Glauber Costa
2011-12-06 20:21 ` [tip:sched/core] sched/accounting: Re-use " tip-bot for Glauber Costa
2011-12-01 10:56 ` [PATCH v2 0/3] cpuacct cgroup refactoring Peter Zijlstra
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=1322498719-2255-1-git-send-email-glommer@parallels.com \
--to=glommer@parallels.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=daniel.lezcano@free.fr \
--cc=devel@openvz.org \
--cc=jbottomley@parallels.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=paul@paulmenage.org \
--cc=pjt@google.com \
/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