On Thu, Dec 04, 2014 at 02:28:10PM -0600, Christoph Lameter wrote: > On Thu, 4 Dec 2014, Leonard Crestez wrote: > > > Yes, we are actually experiencing issues with this. We create lots of virtual > > net_devices and routes, which means lots of percpu counters/pointers. In particular > > we are getting worse performance than in older kernels because the net_device refcnt > > is now a percpu counter. We could turn that back into a single integer but this > > would negate an upstream optimization. > > Well this is not a common use case and that is not what the per cpu > allocator was designed for. There is bound to be signifcant fragmentation > with the current design. The design was for rare allocations when > structures are initialized. ... except that somebody has not known that and took refcounts on e.g. vfsmounts into percpu. With massive amounts of hilarity once docker folks started to test the workloads that created/destroyed those in large amounts. > > Having a "properly scalable" percpu allocator would be quite nice indeed. > > I guess we would be looking at a redesign of the allocator then. FWIW, I think I've already dealt with most of the crap, but I've no idea if networking-related callers end up with similar use patterns. For vfsmounts it seems to suffice... -- 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>