On 09/22/2014 10:57 PM, Hui Zhu wrote: > The cause of this issue is when free memroy size is low and a lot of task is > trying to shrink the memory, the task that is killed by lowmemkiller cannot get > CPU to exit itself. > > Fix this issue with change the scheduling policy to SCHED_FIFO if a task's flag > is TIF_MEMDIE in lowmemkiller. Is it actually true that the task that was killed by lowmemkiller cannot get CPU time? It is also possible that the task is busy in the kernel, for example in the reclaim code, and is not breaking out of some loop fast enough, despite the TIF_MEMDIE flag being set. I suspect SCHED_FIFO simply papers over that kind of issue, by not letting anything else run until the task is gone, instead of fixing the root cause of the problem. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
