From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [proc.txt] Fix /proc/pid/statm documentation From: Albert Cahalan In-Reply-To: <283440000.1091825375@flay> References: <1091754711.1231.2388.camel@cube> <20040806094037.GB11358@k3.hellgate.ch> <20040806104630.GA17188@holomorphy.com> <20040806120123.GA23081@k3.hellgate.ch> <1091800948.1231.2454.camel@cube> <20040806170832.GA898@k3.hellgate.ch> <1091805296.3547.2522.camel@cube> <283440000.1091825375@flay> Content-Type: text/plain Message-Id: <1091817534.1232.2542.camel@cube> Mime-Version: 1.0 Date: 06 Aug 2004 14:38:54 -0400 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: "Martin J. Bligh" Cc: Albert Cahalan , Roger Luethi , William Lee Irwin III , linux-kernel mailing list , linux-mm@kvack.org List-ID: 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: aart@kvack.org