Re: [PATCH v3 0/3] mm: kmemleak: Use a memory pool for kmemleak object allocations

2019-08-13 Thread Catalin Marinas
On Mon, Aug 12, 2019 at 02:07:30PM -0700, Andrew Morton wrote: > On Mon, 12 Aug 2019 17:06:39 +0100 Catalin Marinas > wrote: > > > Following the discussions on v2 of this patch(set) [1], this series > > takes slightly different approach: > > > > - it implements its own simple memory pool that

Re: [PATCH v3 0/3] mm: kmemleak: Use a memory pool for kmemleak object allocations

2019-08-12 Thread Andrew Morton
On Mon, 12 Aug 2019 17:06:39 +0100 Catalin Marinas wrote: > Following the discussions on v2 of this patch(set) [1], this series > takes slightly different approach: > > - it implements its own simple memory pool that does not rely on the > slab allocator > > - drops the early log buffer

[PATCH v3 0/3] mm: kmemleak: Use a memory pool for kmemleak object allocations

2019-08-12 Thread Catalin Marinas
Following the discussions on v2 of this patch(set) [1], this series takes slightly different approach: - it implements its own simple memory pool that does not rely on the slab allocator - drops the early log buffer logic entirely since it can now allocate metadata from the memory pool