From: Li Zefan <lizefan@huawei.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] sched: Split cpuacct
Date: Fri, 29 Mar 2013 13:56:13 +0800 [thread overview]
Message-ID: <51552CFD.3070704@huawei.com> (raw)
In-Reply-To: <5153C2D6.7050103@huawei.com>
Please ignore this patchset. It's not based on the right kernel
version..
On 2013/3/28 12:11, Li Zefan wrote:
> - This patchset splits cpuacct out of core scheduler code.
> - Plus two small optimizations.
>
> 0001-sched-Split-cpuacct-code-out-of-core.c.patch
> 0002-sched-Split-cpuacct-out-of-sched.h.patch
> 0003-cpuacct-Add-cpuacct_init.patch
> 0004-cpuacct-Add-cpuacct_acount_field.patch
> 0005-cpuacct-Remove-redundant-NULL-checks-in-cpuacct_char.patch
> 0006-cpuacct-Remove-redundant-NULL-checks-in-cpuacct_acou.patch
> 0007-cpuacct-Clean-up-cpuacct.h.patch
>
> ---
> kernel/sched/Makefile | 1 +
> kernel/sched/core.c | 228 +----------------------------------------------
> kernel/sched/cpuacct.c | 303 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> kernel/sched/cpuacct.h | 22 +++++
> kernel/sched/cputime.c | 18 +---
> kernel/sched/sched.h | 49 +----------
> 6 files changed, 330 insertions(+), 291 deletions(-)
>
prev parent reply other threads:[~2013-03-29 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 4:11 [PATCH 0/7] sched: Split cpuacct Li Zefan
2013-03-28 4:11 ` [PATCH 1/7] sched: Split cpuacct code out of core.c Li Zefan
2013-03-28 4:12 ` [PATCH 2/7] sched: Split cpuacct out of sched.h Li Zefan
2013-03-28 4:12 ` [PATCH 3/7] cpuacct: Add cpuacct_init() Li Zefan
2013-03-28 4:12 ` [PATCH 4/7] cpuacct: Add cpuacct_acount_field() Li Zefan
2013-03-28 4:12 ` [PATCH 5/7] cpuacct: Remove redundant NULL checks in cpuacct_charge() Li Zefan
2013-03-28 4:13 ` [PATCH 6/7] cpuacct: Remove redundant NULL checks in cpuacct_acount_field() Li Zefan
2013-03-28 4:13 ` [PATCH 7/7] cpuacct: Clean up cpuacct.h Li Zefan
2013-03-29 5:56 ` Li Zefan [this message]
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=51552CFD.3070704@huawei.com \
--to=lizefan@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).