From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755315AbcBCW6M (ORCPT ); Wed, 3 Feb 2016 17:58:12 -0500 Received: from mail-pf0-f170.google.com ([209.85.192.170]:35827 "EHLO mail-pf0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754276AbcBCW6I (ORCPT ); Wed, 3 Feb 2016 17:58:08 -0500 Date: Wed, 3 Feb 2016 14:58:06 -0800 (PST) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Michal Hocko cc: Andrew Morton , Linus Torvalds , Johannes Weiner , Mel Gorman , Tetsuo Handa , Hillf Danton , KAMEZAWA Hiroyuki , linux-mm@kvack.org, LKML Subject: Re: [PATCH 0/3] OOM detection rework v4 In-Reply-To: <20160203132718.GI6757@dhcp22.suse.cz> Message-ID: References: <1450203586-10959-1-git-send-email-mhocko@kernel.org> <20160203132718.GI6757@dhcp22.suse.cz> 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 On Wed, 3 Feb 2016, Michal Hocko wrote: > Hi, > this thread went mostly quite. Are all the main concerns clarified? > Are there any new concerns? Are there any objections to targeting > this for the next merge window? Did we ever figure out what was causing the oom killer to be called much earlier in Tetsuo's http://marc.info/?l=linux-kernel&m=145096089726481 and http://marc.info/?l=linux-kernel&m=145130454913757 ? I'd like to take a look at the patch(es) that fixed it.