From: Ken Chen <kenchen@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"menage@google.com" <menage@google.com>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
mingo@elte.hu,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH] change cpuacct usage percpu format v2
Date: Fri, 27 Feb 2009 12:13:10 -0800 [thread overview]
Message-ID: <b040c32a0902271213q3dd1931foc2b955d8a028eb6f@mail.gmail.com> (raw)
In-Reply-To: <20090227162928.6225fc80.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, Feb 26, 2009 at 11:29 PM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> cpuacct.usage_percpu shows per cpu usage information via cgroupfs.
> It shows all "present" cpus information and "whose information ?"
> is explained just by index of data implicitly.
>
> IIRC, there is physical cpu hotplug system and it can remove
> cpus and change map. Considering a software which records
> this information pediodically(like sar), its better to show id of cpu
> in explict way.
The new format carries a lot of overhead. I would think user space
software can record /sys/devices/system/cpu/present and use that to
map cpu index.
- Ken
next prev parent reply other threads:[~2009-02-27 20:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 5:05 [PATCH] change cpuacct usage percpu format KAMEZAWA Hiroyuki
2009-02-27 6:39 ` Balbir Singh
2009-02-27 6:55 ` KAMEZAWA Hiroyuki
2009-02-27 7:01 ` Balbir Singh
2009-02-27 7:03 ` Li Zefan
2009-02-27 7:05 ` KAMEZAWA Hiroyuki
2009-02-27 7:29 ` [PATCH] change cpuacct usage percpu format v2 KAMEZAWA Hiroyuki
2009-02-27 7:55 ` Paul Menage
2009-02-27 8:02 ` KAMEZAWA Hiroyuki
2009-02-27 20:13 ` Ken Chen [this message]
2009-02-27 23:34 ` KAMEZAWA Hiroyuki
2009-02-28 0:00 ` Ken Chen
2009-02-28 0:14 ` KAMEZAWA Hiroyuki
2009-02-28 0:42 ` KAMEZAWA Hiroyuki
2009-02-28 1:11 ` Dhaval Giani
2009-02-28 5:25 ` KAMEZAWA Hiroyuki
2009-02-28 9:24 ` Dhaval Giani
2009-02-28 9:37 ` KAMEZAWA Hiroyuki
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=b040c32a0902271213q3dd1931foc2b955d8a028eb6f@mail.gmail.com \
--to=kenchen@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--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
all inboxes | Powered by JetHome®