On Fri, Aug 19, 2016 at 01:56:11PM -0700, Andi Kleen wrote: > > Nobody gets a cpu number just to get a cpu number - it's not a useful > > thing to benchmark. What does getcpu() so much that we care? > > malloc is the primary target I believe. Saves lots of memory to keep > caches per CPU rather than per thread. Also improves locality; that does seem like a good idea. Has anyone written and tested the corresponding changes to a malloc implementation? - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
