On Fri 29-04-16 20:54:13, Aaron Lu wrote: > On Fri, Apr 29, 2016 at 11:29:36AM +0200, Michal Hocko wrote: > > On Fri 29-04-16 16:59:37, Aaron Lu wrote: > > > On Thu, Apr 28, 2016 at 01:21:35PM +0200, Michal Hocko wrote: > > > > All of them are order-2 and this was a known problem for "mm, oom: > > > > rework oom detection" commit and later should make it much more > > > > resistant to failures for higher (!costly) orders. So I would definitely > > > > encourage you to retest with the current _complete_ mmotm tree. > > > > > > OK, will run the test on this branch: > > > https://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git since-4.5 > > > with head commit: > > > commit 81cc2e6f1e8bd81ebc7564a3cd3797844ee1712e > > > Author: Michal Hocko <mhocko@xxxxxxxx> > > > Date: Thu Apr 28 12:03:24 2016 +0200 > > > > > > drm/amdgpu: make amdgpu_mn_get wait for mmap_sem killable > > > > > > Please let me know if this isn't right. > > > > Yes that should contain all the oom related patches in the mmotm tree. > > The test shows commit 81cc2e6f1e doesn't OOM anymore and its throughput > is 43609, the same level compared to 43802, so everyting is fine :-) Thanks a lot for double checking! This is highly appreciated! -- Michal Hocko SUSE Labs -- 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>