On 12/21/2015 07:40 PM, Laura Abbott wrote: > + The tradeoff is performance impact. The noticible impact can vary > + and you are advised to test this feature on your expected workload > + before deploying it
What if instead of writing SLAB_MEMORY_SANITIZE_VALUE, we wrote 0's? That still destroys the information, but it has the positive effect of allowing a kzalloc() call to avoid zeroing the slab object. It might mitigate some of the performance impact. If this is on at compile time, but booted with sanitize_slab=off, is there a performance impact? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
