On Sun, 30 Sep 2018, Pingfan Liu wrote: > > > In the debug case the slab needs to be deactivated. Otherwise the > > > slowpath will not be used and debug checks on the following objects will > > > not be done. > > > > After taking a more closely look at the debug code, I consider whether > the alloc_debug_processing() can be also called after get_freelist(s, > page), then deactivate_slab() is not required . My justification is > the debug code will take the same code path as the non-debug, hence > the page will experience the same transition on different list like > the non-debug code, and help to detect the bug, also it will improve > scalability on SMP. > Besides this, I found the debug code is not scalable well, is it worth > to work on it? The debug code is kept out of the hot path intentionally because it does not scale well and reduces performance. Its compiled in in case we have to track down a nasty memory corruption bug on a prod kernel that cannot be easily rebuilt.
