On 2016/9/12 19:13, Michal Hocko wrote: > On Mon 12-09-16 17:51:06, zhong jiang wrote: > [...] >> hi, Michal >> oom reaper indeed can accelerate the recovery of memory, but the patch >> solve the extreme scenario, I hit it by runing trinity. I think the >> scenario can happen whether oom reaper or not. > could you be more specific about the case when the oom reaper and the > current oom code led to the oom deadlock? It is not the oom deadlock. It will lead to hungtask. The explain is as follows. process A occupy a resource and lock it. then A need to allocate memory when memory is very low. at the some time, oom will come up and return directly. because it find other process is freeing memory in same zone. however, the freed memory is taken away by another process. it will lead to A oom again and again. process B still wait some resource holded by A. so B will obtain the lock until A release the resource. therefor, if A spend much time to obtain memory, B will hungtask. Thanks zhongjiang -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>