On 2015/6/5 2:41, Dave Hansen wrote: > On 06/04/2015 06:02 AM, Xishi Qiu wrote: >> Add a new interface in path /proc/sys/vm/mirrorable. When set to 1, it means >> we should allocate mirrored memory for both user and kernel processes. > > That's a pretty dangerously short name. :) >
Hi Dave, Thanks for your comment. I'm not sure whether we should add this interface for user processes. However some important userspace(e.g. /bin/init, key business like datebase) may be want mirrored memory to improve reliability. If we want this interface, I think the code need more change. Thanks, Xishi Qiu > How would this end up getting used? It seems like it would be dangerous > to use once userspace was very far along. So would the kernel set it to > 1 and then let (early??) userspace set it back to 0? That would let > important userspace like /bin/init get mirrored memory without having to > actually change much in userspace. > > This definitely needs some good documentation. > > Also, if it's insane to turn it back *on*, maybe it should be a one-way > trip to turn off. > > . > -- 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/