On Fri, Jul 12, 2013 at 11:15:06AM +0200, Ingo Molnar wrote: > > * Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > > We need those files anyway.. The current proposal is that the entire VMA > > has a single userspace pointer in it. Or rather a 64bit value. > > Yes but accessible via /proc/<PID>/mem or so? *shudder*.. yes. But you're again opening two files. The only advantage of this over userspace writing its own files is that the kernel cleans things up for you. However from what I understood android runs apps as individual users, and I think we can do per user tmpfs mounts. So app dies, user exits, mount goes *poof*. > I was thinking about it in the context of its original purpose: naming > heap areas, which are pretty anonymous right now - /proc/*/maps is full > of mystery ranges today. It is.. although I've myself never had trouble with that. Most every memory debugging that I've used/written over the past two decades was adequately able to identify memory regions. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>