All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Roger Luethi <rl@hellgate.ch>
Cc: 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 07:07:14 -0700	[thread overview]
Message-ID: <20040806140714.GG17188@holomorphy.com> (raw)
In-Reply-To: <20040806135756.GA21411@k3.hellgate.ch>

On Fri, 06 Aug 2004 05:11:18 -0700, William Lee Irwin III wrote:
>> Some of the 2.4 semantics just don't make sense. I would not find it
>> difficult to explain what I believe correct semantics to be in a written
>> document.

On Fri, Aug 06, 2004 at 03:57:56PM +0200, Roger Luethi wrote:
> IMO this is a must for such files (and be it only some comments above
> the code implementing them). I'm afraid that statm is carrying too much
> historical baggage, though -- you would add yet another interpretation
> of those 7 fields.
> Tools reading statm would have to be updated anyway, so I'd rather
> think about what could be done with a new (or just different) file.

Okay, could you write up a "specification" for what you want reported,
then I can cook up a new file or some such for you?

Thanks.


-- wli

WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Roger Luethi <rl@hellgate.ch>
Cc: 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 07:07:14 -0700	[thread overview]
Message-ID: <20040806140714.GG17188@holomorphy.com> (raw)
In-Reply-To: <20040806135756.GA21411@k3.hellgate.ch>

On Fri, 06 Aug 2004 05:11:18 -0700, William Lee Irwin III wrote:
>> Some of the 2.4 semantics just don't make sense. I would not find it
>> difficult to explain what I believe correct semantics to be in a written
>> document.

On Fri, Aug 06, 2004 at 03:57:56PM +0200, Roger Luethi wrote:
> IMO this is a must for such files (and be it only some comments above
> the code implementing them). I'm afraid that statm is carrying too much
> historical baggage, though -- you would add yet another interpretation
> of those 7 fields.
> Tools reading statm would have to be updated anyway, so I'd rather
> think about what could be done with a new (or just different) file.

Okay, could you write up a "specification" for what you want reported,
then I can cook up a new file or some such for you?

Thanks.


-- wli
--
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>

  reply	other threads:[~2004-08-06 14:07 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06  1:11 [proc.txt] Fix /proc/pid/statm documentation Albert Cahalan
2004-08-06  3:48 ` William Lee Irwin III
2004-08-06  9:40 ` Roger Luethi
2004-08-06 10:46   ` William Lee Irwin III
2004-08-06 12:01     ` Roger Luethi
2004-08-06 12:01       ` Roger Luethi
2004-08-06 12:11       ` William Lee Irwin III
2004-08-06 12:11         ` William Lee Irwin III
2004-08-06 13:57         ` Roger Luethi
2004-08-06 13:57           ` Roger Luethi
2004-08-06 14:07           ` William Lee Irwin III [this message]
2004-08-06 14:07             ` William Lee Irwin III
2004-08-06 15:02             ` Roger Luethi
2004-08-06 15:02               ` Roger Luethi
2004-08-06 14:02       ` Albert Cahalan
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 17:08           ` Roger Luethi
2004-08-06 15:14           ` Albert Cahalan
2004-08-06 15:14             ` Albert Cahalan
2004-08-06 20:49             ` Martin J. Bligh
2004-08-06 20:49               ` Martin J. Bligh
2004-08-06 18:38               ` Albert Cahalan
2004-08-06 18:38                 ` Albert Cahalan
2004-08-06 21:15                 ` Martin J. Bligh
2004-08-06 21:15                   ` Martin J. Bligh
2004-08-07 17:37         ` Paul Jackson
2004-08-07 17:37           ` Paul Jackson
2004-08-06 12:58   ` Albert Cahalan
2004-08-06 12:58     ` Albert Cahalan
2004-08-06 15:48     ` William Lee Irwin III
2004-08-06 15:48       ` William Lee Irwin III
2004-08-06 14:14       ` Albert Cahalan
2004-08-06 14:14         ` Albert Cahalan
2004-08-06 16:49         ` William Lee Irwin III
2004-08-06 16:49           ` William Lee Irwin III
2004-08-06 16:34     ` Roger Luethi
2004-08-06 16:34       ` Roger Luethi
2004-08-06 14:51       ` Albert Cahalan
2004-08-06 14:51         ` Albert Cahalan
2004-08-06 17:28         ` Martin J. Bligh
2004-08-06 17:28           ` Martin J. Bligh
2004-08-06 18:21         ` Roger Luethi
2004-08-06 18:21           ` Roger Luethi
  -- strict thread matches above, loose matches on Subject: below --
2004-08-05 17:10 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=20040806140714.GG17188@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=albert@users.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rl@hellgate.ch \
    /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.