On Fri, Feb 24, 2012 at 9:42 PM, Mike Frysinger <vapier@xxxxxxxxxx> wrote: >> I like the idea of marking all stack vmas with their task ids but it >> will most likely break procps. > > how ? I don't know yet, since I haven't looked at the procps code. I intend to do that once the patch is stable. But I imagine it would look for "[stack]" or something similar in the output. It ought to be easy enough to change I guess. >> Besides, I think it could be done within procps with this change rather than >> having the kernel do it. > > how exactly is procps supposed to figure this out ? /proc/<pid>/maps shows the > pid's main stack, as does /proc/<pid>/tid/*/maps. Since the maps are essentially the same, it would require pmap for example, to read through the PID/maps as well as TID/maps and associate them. I understand now that this may be a little racy. I'll include thread ids and see how procps copes with it. -- Siddhesh Poyarekar http://siddhesh.in -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
