From: Roger Luethi <rl@hellgate.ch>
To: William Lee Irwin III <wli@holomorphy.com>,
Albert Cahalan <albert@users.sf.net>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [proc.txt] Fix /proc/pid/statm documentation
Date: Fri, 6 Aug 2004 14:01:23 +0200 [thread overview]
Message-ID: <20040806120123.GA23081@k3.hellgate.ch> (raw)
In-Reply-To: <20040806104630.GA17188@holomorphy.com>
[ fixed linux-mm address ]
On Fri, 06 Aug 2004 03:46:30 -0700, William Lee Irwin III wrote:
> On Fri, Aug 06, 2004 at 11:40:37AM +0200, Roger Luethi wrote:
> > I discussed this very issue with wli on linux-mm about a year ago. proc
> > file and documentation are still broken. So what's wrong with doing
> > something about it?
>
> So now what, you want me to do yet another forward port of
> linux-2.4.9-statm-B1.diff?
Your call, obviously -- do you think it's worthwhile? I didn't CC you
on my initial posting because I wanted to avoid the impression that I am
trying to make this your problem somehow. Priorities as I see them are:
- Document statm content somewhere. I posted a patch to document
the current state. It could be complemented with a description of
what it is supposed to do.
- Come to some agreement on what the proper values should be and
change kernels accordingly. I'm inclined to favor keeping the first two
(albeit redundant) fields and setting the rest to 0, simply because for
them too many different de-facto semantics live in exisiting kernels.
A year ago, the first field was broken in 2.4 as well (not sure if/when
it got fixed), but I can see why it is useful to keep around until top
has found a better source. Same for the second field, the only one that
has always been correct AFAIK.
- Provide additional information in proc files other than statm.
The problems with undocumented records are evident, but
/proc/pid/status may be getting too heavy for frequent parsing. It's
not realistic to redesign proc at this point, but it would be nice
to have some documented understanding about the direction of proc
evolution.
Roger
--
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 parent reply other threads:[~2004-08-06 12:01 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 [this message]
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
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=20040806120123.GA23081@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=albert@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox