From: William Lee Irwin III <wli@holomorphy.com>
To: Anton Blanchard <anton@samba.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@zip.com.au, riel@surriel.com
Subject: Re: statm_pgd_range() sucks!
Date: Fri, 30 Aug 2002 01:31:00 -0700 [thread overview]
Message-ID: <20020830083100.GQ18114@holomorphy.com> (raw)
In-Reply-To: <20020830082456.GC10656@krispykreme>
At some point in the past, I wrote:
>> Okay, I have *had it* with statm_pgd_range()!
On Fri, Aug 30, 2002 at 06:24:56PM +1000, Anton Blanchard wrote:
> On a related note, it would be nice if procps would not parse things it
> doesnt need:
> strace ps 2>&1 | grep open | grep '/proc'
> open("/proc/12467/stat", O_RDONLY) = 7
> open("/proc/12467/statm", O_RDONLY) = 7
> open("/proc/12467/status", O_RDONLY) = 7
> open("/proc/12467/cmdline", O_RDONLY) = 7
> open("/proc/12467/environ", O_RDONLY) = 7
> It always opens statm even when its not required.
> Anton
Userspace is FITH, it only needs to do it for BSD-style stuff reporting
RSS/vsz. vsz is wrong anyway if it doesn't open /proc/$PID/maps.
Cheers,
Bill
--
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/
prev parent reply other threads:[~2002-08-30 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 1:58 William Lee Irwin III
2002-08-30 2:51 ` Andrew Morton
2002-08-30 3:12 ` William Lee Irwin III
2002-08-30 3:54 ` Andrew Morton
2002-08-30 17:45 ` Gerrit Huizenga
2002-09-01 22:02 ` Daniel Phillips
2002-09-05 3:20 ` William Lee Irwin III
2002-09-05 4:48 ` Andrew Morton
2002-09-05 6:05 ` William Lee Irwin III
2002-09-05 6:49 ` Andrew Morton
2002-09-05 7:07 ` William Lee Irwin III
2002-09-05 6:22 ` William Lee Irwin III
2002-08-30 8:24 ` Anton Blanchard
2002-08-30 8:31 ` William Lee Irwin III [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=20020830083100.GQ18114@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.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