On Thu, 30 Jan 2014, Andrew Morton wrote: > > Why? We already construct the name in memcg_create_kmem_cache() > > appropriately, we just want to avoid the kstrdup() in > > kmem_cache_create_memcg() since it's pointless like my patch does. > > oh, OK, missed that. > > The problem now is that the string at kmem_cache.name is PATH_MAX > bytes, and PATH_MAX is huuuuuuuge. > It always was. Google uses pretty long memcg names (although admittedly not as long as PATH_MAX!) and it hasn't caused any problem with /proc/slabinfo or slabtop(1). -- 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>