Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752668AbcCVWI0 (ORCPT ); Tue, 22 Mar 2016 18:08:26 -0400 Received: from mail-pf0-f178.google.com ([209.85.192.178]:36565 "EHLO mail-pf0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752174AbcCVWIX (ORCPT ); Tue, 22 Mar 2016 18:08:23 -0400 Date: Tue, 22 Mar 2016 15:08:21 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Michal Hocko , Tetsuo Handa cc: Andrew Morton , linux-mm@kvack.org, LKML , Ingo Molnar , Johannes Weiner , Mel Gorman , Michal Hocko , Oleg Nesterov , Peter Zijlstra , Vladimir Davydov Subject: Re: [PATCH 0/9] oom reaper v6 In-Reply-To: <1458644426-22973-1-git-send-email-mhocko@kernel.org> Message-ID: References: <1458644426-22973-1-git-send-email-mhocko@kernel.org> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1741 Lines: 35 On Tue, 22 Mar 2016, Michal Hocko wrote: > Hi, > I am reposting the whole patchset on top of the current Linus tree which should > already contain big pile of Andrew's mm patches. This should serve an easier > reviewability and I also hope that this core part of the work can go to 4.6. > > The previous version was posted here [1] Hugh and David have suggested to > drop [2] because the munlock path currently depends on the page lock and > it is better if the initial version was conservative and prevent from > any potential lockups even though it is not clear whether they are real > - nobody has seen oom_reaper stuck on the page lock AFAICK. Me or Hugh > will have a look and try to make the munlock path not depend on the page > lock as a follow up work. > > Apart from that the feedback revealed one bug for a very unusual > configuration (sysctl_oom_kill_allocating_task) and that has been fixed > by patch 8 and one potential mis interaction with the pm freezer fixed by > patch 7. > > I think the current code base is already very useful for many situations. > The rest of the feedback was mostly about potential enhancements of the > current code which I would really prefer to build on top of the current > series. I plan to finish my mmap_sem killable for write in the upcoming > release cycle and hopefully have it merged in the next merge window. > I believe more extensions will follow. > > This code has been sitting in the mmotm (thus linux-next) for a while. > Are there any fundamental objections to have this part merged in this > merge window? > Tetsuo, have you been able to run your previous test cases on top of this version and do you have any concerns about it or possible extensions that could be made?