> > BTW, something odd happened to mm/memory.c - either a mangled patch > > or a lost followup: > > commit ea1e7ed33708 > > mm: create a separate slab for page->ptl allocation > > Fair enough, and yes, it does create that separate slab. The problem > > is, it's still using kmalloc/kfree for those beasts - > > page_ptl_cachep isn't used at all... * Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> [2013-11-20 14:33]: > Ok, it looks straightforward enough to just replace the kmalloc/kfree > with using a slab allocation using the page_ptl_cachep pointer. I'd do > it myself, but I would like to know how it got lost? Also, much > testing to make sure the cachep is initialized early enough. The initial sending had the proper hunks at the end, so something really got lost afterwards... https://lkml.org/lkml/2013/10/22/129 -- Damien Wyart -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
