From: Pavel Machek <pavel@suse.cz>
To: Andreas Dilger <adilger@turbolinux.com>, Zach Brown <zab@osdlab.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] struct kernel_stat -> struct cpu_stat[NR_CPUS]
Date: Wed, 11 Jul 2001 23:53:12 +0200 [thread overview]
Message-ID: <20010711235312.A425@bug.ucw.cz> (raw)
In-Reply-To: <20010702163631.B9806@osdlab.org> <200107030649.f636nqB3001452@webber.adilger.int>
In-Reply-To: <200107030649.f636nqB3001452@webber.adilger.int>; from Andreas Dilger on Tue, Jul 03, 2001 at 12:49:51AM -0600
Hi!
> > These per cpu statistics are reported via a new /proc/cpustat, a quick
> > tool for processing that output, vmstat-style, can be found near
>
> Could you consider /proc/cpu/0/stats or similar? It is much nicer
> than polluting the top-level /proc directory, and I believe there
> are a bunch of other per-cpu items waiting to go there as well
> (process binding, hot-swap CPU stuff, etc)
Add throttling, C-states, and similar acpi stuff. I'd like it to go
into /proc/cpu/0 rather than be buried somewhere into /proc/acpi.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
prev parent reply other threads:[~2001-07-12 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 23:36 [RFC][PATCH] struct kernel_stat -> struct cpu_stat[NR_CPUS] Zach Brown
2001-07-03 6:49 ` Andreas Dilger
2001-07-11 21:53 ` Pavel Machek [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=20010711235312.A425@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zab@osdlab.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