I'm trying to arrange for a process to have a different memory policy on its stack as compared to everything else (e.g. mapped libraries). Before I start looking for kludges, is there any clean way to do this?
So far, the best I can come up with is to either parse /proc/self/maps on startup or to deduce the stack range from the stack pointer and then call mbind. Then, for added fun, I'll need to hook mmap so that I can mbind MAP_STACK vmas that are created for threads. This is awful. Is there something better? (What I really want is a separate policy for MAP_SHARED vs MAP_PRIVATE.) --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
