From: Robert Love <rml@tech9.net>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: David Chow <davidchow@shaolinmicro.com>, linux-kernel@vger.kernel.org
Subject: Re: CPU load
Date: 10 Jul 2002 10:49:29 -0700 [thread overview]
Message-ID: <1026323370.1352.70.camel@sinai> (raw)
In-Reply-To: <20020710165443.GA15916@holomorphy.com>
On Wed, 2002-07-10 at 09:54, William Lee Irwin III wrote:
> Examine the avenrun array declared in kernel/timer.c in a manner similar
> to how loadavg_read_proc() in fs/proc/proc_misc.c does.
David, I wanted to add that we formalized the locking rules on
avenrun[3] a couple kernel revisions ago.
In 2.4, I believe it is implicitly assumed you will do a cli() before
accessing the data (if you want all 3 values to be in sync you need the
read to be safe).
In 2.5, grab a read_lock on xtime_lock and go at it.
Robert Love
next prev parent reply other threads:[~2002-07-10 17:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 14:50 CPU load David Chow
2002-07-10 16:54 ` William Lee Irwin III
2002-07-10 17:49 ` Robert Love [this message]
2002-07-26 17:38 ` David Chow
2007-02-12 5:33 Vassili Karpov
2007-02-12 5:44 ` Con Kolivas
2007-02-12 5:54 ` malc
2007-02-12 6:12 ` Con Kolivas
2007-02-12 7:10 ` malc
2007-02-12 7:29 ` Con Kolivas
2007-02-12 5:55 ` Stephen Rothwell
2007-02-12 6:08 ` Con Kolivas
2007-02-12 14:32 ` Pavel Machek
2007-02-13 22:01 ` malc
2007-02-13 22:08 ` Con Kolivas
2007-02-14 7:28 ` malc
2007-02-14 8:09 ` Con Kolivas
2007-02-14 20:45 ` Pavel Machek
2007-02-25 10:35 ` malc
2007-02-26 9:28 ` Pavel Machek
2007-02-26 10:42 ` malc
2007-02-26 16:38 ` Randy Dunlap
2007-02-12 18:05 ` malc
2007-02-12 16:57 Andrew Burgess
2007-02-12 18:15 ` malc
2018-03-27 11:44 CPU Load Ryan Meulenkamp
2018-03-29 1:24 ` Andre McCurdy
2018-03-29 6:42 ` Jussi Laako
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=1026323370.1352.70.camel@sinai \
--to=rml@tech9.net \
--cc=davidchow@shaolinmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.