From: Ingo Molnar <mingo@elte.hu>
To: Ken Chen <kenchen@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/2] cpuacct: refactoring cpuusage_read / cpuusage_write
Date: Tue, 16 Dec 2008 12:15:26 +0100 [thread overview]
Message-ID: <20081216111526.GC4299@elte.hu> (raw)
In-Reply-To: <b040c32a0812152202y4914ba88gbf0c9137d50a296a@mail.gmail.com>
* Ken Chen <kenchen@google.com> wrote:
> In the thread regarding to 'export percpu cpuacct cgroup stats'
> http://lkml.org/lkml/2008/12/7/13
>
> akpm pointed out that current cpuacct code is inefficient. This patch
> refactoring the following:
>
> * make cpu_rq locking only on 32-bit
> * change iterator to each_present_cpu instead of each_possible_cpu to
> make it hotplug friendly.
>
> It's a bit of code churn, but I was rewarded with 160 byte code size saving
> on x86-64 arch and zero code size change on i386.
applied to tip/sched/core, thanks Ken!
Ingo
prev parent reply other threads:[~2008-12-16 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 6:02 Ken Chen
2008-12-16 11:15 ` Ingo Molnar [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=20081216111526.GC4299@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@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
all inboxes | Powered by JetHome®