From: Benjamin LaHaise <bcrl@bcrl.kvack.org>
To: "Richard F. Rebel" <rrebel@whenu.com>
Cc: Hugh Dickins <hugh@veritas.com>, linux-kernel@vger.kernel.org
Subject: Re: /proc/*/statm, exactly what does "shared" mean?
Date: Wed, 16 Feb 2005 09:52:20 -0500 [thread overview]
Message-ID: <20050216145220.GA10400@kvack.org> (raw)
In-Reply-To: <1108219160.12693.184.camel@blue.obulous.org>
On Sat, Feb 12, 2005 at 09:39:20AM -0500, Richard F. Rebel wrote:
> That said, many mod_perl users are *VERY* interested in being able to
> detect and observe how "shared" our forked children are. Shared meaning
> private pages shared with children (copy on write). Is it even possible
> to do this in 2.6 kernels? If so, any pointers would be very helpful.
One thing Hugh didn't mention is the background as to why the shared
statistic was changed: it comes back to the fact that it was a very
expensive statistic to calculate. People running top on systems with
lots of virtual memory in use (ie lots of processes, applications with
shared memory segments) were seeing ridiculous cpu usage (100% for seconds
at a time) by top. As a result, the statistics available from the statm
file were changed to counters making the read of statm an O(1) operation.
This dropped top's cpu usage on a busy system to a much more reasonable
<1%, making it possible to get an idea what a busy system is actually
busy with.
-ben
prev parent reply other threads:[~2005-02-16 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 22:32 /proc/*/statm, exactly what does "shared" mean? Richard F. Rebel
2005-02-12 13:06 ` Hugh Dickins
2005-02-12 14:39 ` Richard F. Rebel
2005-02-12 15:42 ` Hugh Dickins
2005-02-16 10:41 ` Mauricio Lin
2005-02-16 12:00 ` Hugh Dickins
2005-02-16 15:02 ` Mauricio Lin
2005-02-16 15:17 ` Richard F. Rebel
2005-02-16 16:10 ` Hugh Dickins
2005-02-17 16:33 ` Richard F. Rebel
2005-02-16 15:58 ` Hugh Dickins
2005-02-16 14:52 ` Benjamin LaHaise [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=20050216145220.GA10400@kvack.org \
--to=bcrl@bcrl.kvack.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rrebel@whenu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox