Re: [RFC PATCH 1/2] mempool: do not consume memory reserves from the reclaim path
From: David Rientjes
Date: Tue Jul 19 2016 - 16:46:10 EST
On Tue, 19 Jul 2016, Johannes Weiner wrote:
> Mempool guarantees forward progress by having all necessary memory
> objects for the guaranteed operation in reserve. Think about it this
> way: you should be able to delete the pool->alloc() call entirely and
> still make reliable forward progress. It would kill concurrency and be
> super slow, but how could it be affected by a system OOM situation?
> If our mempool_alloc() is waiting for an object that an OOM victim is
> holding, where could that OOM victim get stuck before giving it back?
> As I asked in the previous thread, surely you wouldn't do a mempool
> allocation first and then rely on an unguarded page allocation to make
> forward progress, right? It would defeat the purpose of using mempools
> in the first place. And surely the OOM victim wouldn't be waiting for
> a lock that somebody doing mempool_alloc() *against the same mempool*
> is holding. That'd be an obvious ABBA deadlock.
> So maybe I'm just dense, but could somebody please outline the exact
> deadlock diagram? Who is doing what, and how are they getting stuck?
> cpu0: cpu1:
> wait for cpu1
> not allocating memory - would defeat mempool
> not taking locks held by cpu0* - would ABBA
> * or any other task that does mempool_alloc(pool0) before unlock
I'm approaching this from a perspective of any possible mempool usage, not
with any single current user in mind.
Any mempool_alloc() user that then takes a contended mutex can do this.
taskA taskB taskC
----- ----- -----
Imagine the mempool_alloc() done by taskA depleting all free elements so
we rely on it to do mempool_free() before any other mempool allocator can
If taskC is oom killed, or has PF_MEMALLOC set, it cannot access memory
reserves from the page allocator if __GFP_NOMEMALLOC is automatic in
mempool_alloc(). This livelocks the page allocator for all processes.
taskB in this case need only stall after taking mutex_lock() successfully;
that could be because of the oom livelock, it is contended on another
mutex held by an allocator, etc.
Obviously taskB stalling while holding a mutex that is contended by a
mempool user holding an element is not preferred, but it's possible. (A
simplified version is also possible with 0-size mempools, which are also
My point is that I don't think we should be forcing any behavior wrt
memory reserves as part of the mempool implementation. In the above,
taskC mempool_alloc() would succeed and not livelock unless
__GFP_NOMEMALLOC is forced. The mempool_alloc() user may construct their
set of gfp flags as appropriate just like any other memory allocator in
The alternative would be to ensure no mempool users ever take a lock that
another thread can hold while contending another mutex or allocating