n Wed, 20 Jan 2016, Laura Abbott wrote: > The SLAB_DEBUG flags force everything to skip the CPU caches which is > causing the slow down. I experimented with allowing the debugging to > happen with CPU caches but I'm not convinced it's possible to do the > checking on the fast path in a consistent manner without adding > locking. Is it worth refactoring the debugging to be able to be used > on cpu caches or should I take the approach here of having the clear > be separate from free_debug_processing? At least posioning would benefit from such work. I think both sanitization and posoning should be done by the same logic. Remove poisoning if necessary. Note though that this security stuff should not have a significant impact on the general case. -- 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>