From: Zach Brown <zab@zabbo.net>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: pmhahn@titan.lahn.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuid/msr + devfs
Date: Mon, 3 Sep 2001 16:34:48 -0400 [thread overview]
Message-ID: <20010903163448.A22633@erasmus.off.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0108121020050.1068-100000@titan.lahn.de> <200109032007.f83K73H27504@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200109032007.f83K73H27504@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Mon, Sep 03, 2001 at 02:07:03PM -0600
> Better to have a central place which creates per-CPU directories,
> which you can call into and grab a directory for a CPU.
I talked with arjan and rmk about this when playing around with per cpu
statistics stuff. Is the proc_cpu.c stuff in the patch useful?
http://www.osdlab.org/sw_resources/cpustat/cpustat-2.4.7.pre5-1.diff
- z
next prev parent reply other threads:[~2001-09-03 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 8:33 Philipp Matthias Hahn
2001-09-03 20:07 ` Richard Gooch
2001-09-03 20:34 ` Zach Brown [this message]
2001-09-03 20:51 ` Richard Gooch
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=20010903163448.A22633@erasmus.off.net \
--to=zab@zabbo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmhahn@titan.lahn.de \
--cc=rgooch@ras.ucalgary.ca \
/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®