From: Albert Cahalan <albert@users.sf.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
Roger Luethi <rl@hellgate.ch>,
William Lee Irwin III <wli@holomorphy.com>,
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 14:38:54 -0400 [thread overview]
Message-ID: <1091817534.1232.2542.camel@cube> (raw)
In-Reply-To: <283440000.1091825375@flay>
On Fri, 2004-08-06 at 16:49, Martin J. Bligh wrote:
> > As long as I can fall back to the old /proc files when truly
> > radical kernel changes happen, exposure of kernel internals
> > isn't a serious problem.
> >
> > If I had the DWARF2 data alone, /dev/mem might be enough.
> > (sadly, "top" would require some major work before I'd trust it)
>
> We did that on PTX ... walking tasklists lockless is a bitch.
It's fast. Lockless tasklist walking looks easy enough.
Find the process, grab the data, then find the process
again. If the process went away, discard the data.
I guess I'd like to have a /dev/ram-only device, for protection
against touching device memory (including AGP mem) by mistake.
It's odd that there doesn't seem to be such a device already.
Without this, I'd need to re-verify much more often.
Any problem I'm not seeing?
WARNING: multiple messages have this Message-ID (diff)
From: Albert Cahalan <albert@users.sf.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
Roger Luethi <rl@hellgate.ch>,
William Lee Irwin III <wli@holomorphy.com>,
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 14:38:54 -0400 [thread overview]
Message-ID: <1091817534.1232.2542.camel@cube> (raw)
In-Reply-To: <283440000.1091825375@flay>
On Fri, 2004-08-06 at 16:49, Martin J. Bligh wrote:
> > As long as I can fall back to the old /proc files when truly
> > radical kernel changes happen, exposure of kernel internals
> > isn't a serious problem.
> >
> > If I had the DWARF2 data alone, /dev/mem might be enough.
> > (sadly, "top" would require some major work before I'd trust it)
>
> We did that on PTX ... walking tasklists lockless is a bitch.
It's fast. Lockless tasklist walking looks easy enough.
Find the process, grab the data, then find the process
again. If the process went away, discard the data.
I guess I'd like to have a /dev/ram-only device, for protection
against touching device memory (including AGP mem) by mistake.
It's odd that there doesn't seem to be such a device already.
Without this, I'd need to re-verify much more often.
Any problem I'm not seeing?
--
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 21:13 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
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 [this message]
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=1091817534.1232.2542.camel@cube \
--to=albert@users.sf.net \
--cc=albert@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--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 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.