From: Pavel Machek <pavel@suse.cz>
To: Zach Brown <zab@osdlab.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] cutting up struct kernel_stat into cpu_stat
Date: Sat, 30 Jun 2001 14:24:39 +0000 [thread overview]
Message-ID: <20010630142438.A255@toy.ucw.cz> (raw)
In-Reply-To: <20010621113107.A16934@osdlab.org>
In-Reply-To: <20010621113107.A16934@osdlab.org>; from zab@osdlab.org on Thu, Jun 21, 2001 at 11:31:07AM -0700
Hi!
> The attached patch-in-progress removes the per-cpu statistics from
> struct kernel_stat and puts them in a cpu_stat structure, one per cpu,
> cacheline padded. The data is still coolated and presented through
> /proc/stat, but another file /proc/cpustat is also added. The locking
> is as nonexistant as it was with kernel_stat, but who cares, they're
> just fuzzy stats to be eyeballed by system tuners :).
Looks good to me... Should improve performance plus adds per-cpu data...
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
prev parent reply other threads:[~2001-07-08 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 18:31 Zach Brown
2001-06-21 20:53 ` Albert D. Cahalan
2001-06-30 14:24 ` 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=20010630142438.A255@toy.ucw.cz \
--to=pavel@suse.cz \
--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
all inboxes | Powered by JetHome®