From: Gerrit Huizenga <gh@us.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
riel@surriel.com
Subject: Re: statm_pgd_range() sucks!
Date: Fri, 30 Aug 2002 10:45:35 -0700 [thread overview]
Message-ID: <E17kppv-0005f8-00@w-gerrit2> (raw)
In-Reply-To: Your message of Thu, 29 Aug 2002 20:12:08 PDT. <20020830031208.GK888@holomorphy.com>
In message <20020830031208.GK888@holomorphy.com>, > : William Lee Irwin III wri
tes:
> I'm basically looking for VSZ, RSS, %cpu, & pid -- after that I don't
> care. top(1) examines a lot more than it feeds into the display, for
> reasons unknown. In principle, there are ways of recovering the other
> bits that seem too complex to be worthy of doing:
Try using "f" inside of top(1). You'll see a set of additional
bits of info that it can report which may map to the data that it
examines but you haven't seen in its display.
gerrit
WARNING: multiple messages have this Message-ID (diff)
From: Gerrit Huizenga <gh@us.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
riel@surriel.com
Subject: Re: statm_pgd_range() sucks!
Date: Fri, 30 Aug 2002 10:45:35 -0700 [thread overview]
Message-ID: <E17kppv-0005f8-00@w-gerrit2> (raw)
In-Reply-To: Your message of Thu, 29 Aug 2002 20:12:08 PDT. <20020830031208.GK888@holomorphy.com>
In message <20020830031208.GK888@holomorphy.com>, > : William Lee Irwin III wri
tes:
> I'm basically looking for VSZ, RSS, %cpu, & pid -- after that I don't
> care. top(1) examines a lot more than it feeds into the display, for
> reasons unknown. In principle, there are ways of recovering the other
> bits that seem too complex to be worthy of doing:
Try using "f" inside of top(1). You'll see a set of additional
bits of info that it can report which may map to the data that it
examines but you haven't seen in its display.
gerrit
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-08-30 17:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 1:58 statm_pgd_range() sucks! William Lee Irwin III
2002-08-30 1:58 ` William Lee Irwin III
2002-08-30 2:51 ` Andrew Morton
2002-08-30 2:51 ` Andrew Morton
2002-08-30 3:12 ` William Lee Irwin III
2002-08-30 3:12 ` William Lee Irwin III
2002-08-30 3:54 ` Andrew Morton
2002-08-30 3:54 ` Andrew Morton
2002-08-30 17:45 ` Gerrit Huizenga [this message]
2002-08-30 17:45 ` Gerrit Huizenga
2002-09-01 22:02 ` Daniel Phillips
2002-09-01 22:02 ` Daniel Phillips
2002-09-05 3:20 ` William Lee Irwin III
2002-09-05 3:20 ` William Lee Irwin III
2002-09-05 4:48 ` Andrew Morton
2002-09-05 4:48 ` Andrew Morton
2002-09-05 6:05 ` William Lee Irwin III
2002-09-05 6:05 ` William Lee Irwin III
2002-09-05 6:49 ` Andrew Morton
2002-09-05 6:49 ` Andrew Morton
2002-09-05 7:07 ` William Lee Irwin III
2002-09-05 7:07 ` William Lee Irwin III
2002-09-05 6:22 ` William Lee Irwin III
2002-09-05 6:22 ` William Lee Irwin III
2002-08-30 8:24 ` Anton Blanchard
2002-08-30 8:24 ` Anton Blanchard
2002-08-30 8:31 ` William Lee Irwin III
2002-08-30 8:31 ` William Lee Irwin III
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=E17kppv-0005f8-00@w-gerrit2 \
--to=gh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--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.