From: Albert Cahalan <albert@users.sf.net>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Roger Luethi <rl@hellgate.ch>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [proc.txt] Fix /proc/pid/statm documentation
Date: 06 Aug 2004 10:14:43 -0400 [thread overview]
Message-ID: <1091801683.1231.2467.camel@cube> (raw)
In-Reply-To: <20040806154834.GL17188@holomorphy.com>
On Fri, 2004-08-06 at 11:48, William Lee Irwin III wrote:
> On Fri, 2004-08-06 at 05:40, Roger Luethi wrote:
> >> And then there is the trade-off between human readable and
> >> easy to parse. ISTR there have been occasional discussions, but maybe
> >> it's time to revisit the issue because the current mess is a problem.
>
> On Fri, Aug 06, 2004 at 08:58:43AM -0400, Albert Cahalan wrote:
> > The current bugs are a problem.
> > Quoting your other email now:
>
> Could you describe those in isolation from other issues?
Whatever Roger found, plus:
1. trs == text RESIDENT size
2. drs == data RESIDENT size
3. memory-mapped devices should be counted for only 1 file
(use an old Linux box running X to see)
I'm not terribly concerned right now. I just don't think
it's OK to go ripping out statm over a few bugs.
If we ripped out every buggy piece of kernel code, we'd
have a 0-byte kernel.
There are far bigger issues elsewhere, like %CPU.
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-08-06 14:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1091754711.1231.2388.camel@cube>
[not found] ` <20040806094037.GB11358@k3.hellgate.ch>
[not found] ` <20040806104630.GA17188@holomorphy.com>
2004-08-06 12:01 ` Roger Luethi
2004-08-06 12:11 ` William Lee Irwin III
2004-08-06 13:57 ` Roger Luethi
2004-08-06 14:07 ` William Lee Irwin III
2004-08-06 15:02 ` Roger Luethi
2004-08-06 14:02 ` Albert Cahalan
2004-08-06 16:48 ` William Lee Irwin III
2004-08-06 17:08 ` Roger Luethi
2004-08-06 15:14 ` Albert Cahalan
2004-08-06 20:49 ` Martin J. Bligh
2004-08-06 18:38 ` Albert Cahalan
2004-08-06 21:15 ` Martin J. Bligh
2004-08-07 17:37 ` Paul Jackson
2004-08-06 12:58 ` Albert Cahalan
2004-08-06 15:48 ` William Lee Irwin III
2004-08-06 14:14 ` Albert Cahalan [this message]
2004-08-06 16:49 ` William Lee Irwin III
2004-08-06 16:34 ` Roger Luethi
2004-08-06 14:51 ` Albert Cahalan
2004-08-06 17:28 ` Martin J. Bligh
2004-08-06 18:21 ` Roger Luethi
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=1091801683.1231.2467.camel@cube \
--to=albert@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rl@hellgate.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox