Messages in this thread | | | Date | Fri, 06 Aug 2004 13:49:35 -0700 | From | "Martin J. Bligh" <> | Subject | Re: [proc.txt] Fix /proc/pid/statm documentation |
| |
>> > If it's going to be this dynamic, then just give me DWARF2 debug >> > info and the raw data. Like this: >> > >> > /proc/DWARF2 >> > /proc/1000/mm_struct >> > /proc/1000/signal_struct >> > /proc/1000/sighand_struct >> > /proc/1000/task/1024/thread_info >> > /proc/1000/task/1024/task_struct >> > /proc/1000/task/1024/fs_struct >> >> That's different. The overhead would be prohibitive. Also, this exposes >> internal kernel structures. > > The overhead? I'm not seeing much, other than the multiple > files and the very fact that field locations are movable. > > 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.
M.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |