mm: avoid order-0 OOMs when there are LMK killable tasks
There is a case reported where there are lot of processes killable by
lowmemorykiller. One of the context P1 is in lowmem_scan holding the
mutex. System is slow due to stress test and P1 is taking time to
complete. This causes other tasks in direct reclaim path deplete their
MAX_RECLAIM_RETRIES and result in OOM. Allow non-costly allocs to retry
till there are no lowmemorykiller killable tasks.
Change-Id: I5532fff6889ad57ab3fb09bebe4b9256eb098e69
Signed-off-by:
Vinayak Menon <vinmenon@codeaurora.org>
Loading
Please register or sign in to comment