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, 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>