Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp1403193imm; Thu, 5 Jul 2018 22:40:51 -0700 (PDT) X-Google-Smtp-Source: AAOMgpftMu0HmbWO4UWwTgJPEZjIaurj8XM9OltpnRq4S9IQTCc1Z5YTJVlZbp3JnBtgkcef1PRX X-Received: by 2002:a17:902:7782:: with SMTP id o2-v6mr8960325pll.93.1530855651338; Thu, 05 Jul 2018 22:40:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530855651; cv=none; d=google.com; s=arc-20160816; b=DXQen0Nc5TRegt8IsnhiSApf6XTn5AwmZw/3z8Q2zmwxLVeMKQhcY8GV2iOBohFWwp HVJbomCHdCapA6gqy7HJt8fdytKZSD/dA0xuPG9zyTsu+BCxXN5WEbojawilmr3TKYWv UXNXzUTgVQtN0df1ai0iJE+sVEULYRWJlFrR6vfBW8s7fOu9uOtbkN3iSPIFPVNUy16b fMHQY3g7sTXXUHArBXGV/SGJqTmgmiYy4IVAw3gpjMDIL61fnNXHcpRUU7R8E5OyQPjW oGha02/1JDzNxQL15i6NhcZkB50in31VowuMju7FXqSo+wBcFR1pg5KFOZMtrxMlpUPq pk1Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=yTgoy1NV91WY/kCIjrCqZ660XbexN4VCx1v8JDeE7bg=; b=dHAcA6e49UElHBFoCmPs8F0TvToQkm40qY8Okuqc3YiiOgecnjeQpSgYq3wJnruUW6 M7bngQXSrrnn8mCX9SXDwTpU4HaMaCxX5lLIzlE/+El4rlfKTwBBoeScVnEGKcS0bWgE CNgbXNE4RaP1XE4m66NL/VJi3mZUhqUq2Ejfx4B+g9pKbHC46nRzUOROFBd0Xp78t2QG OiVyV8BsuYEmdTiYJRkm3ZxHLUJfcIrQBZ/XCOFUY9huBUPqXH0aqjjcENlwL37TDN7n 6sqqpraL5+ahN255RR5mii7HU9y5yBbTv8vC4St1Dd47+ynaG5hz2tlXpwjj5x6Tk/i8 I4CA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l5-v6si7722144pls.360.2018.07.05.22.40.37; Thu, 05 Jul 2018 22:40:51 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932748AbeGFFjq (ORCPT + 99 others); Fri, 6 Jul 2018 01:39:46 -0400 Received: from mx2.suse.de ([195.135.220.15]:56904 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932614AbeGFFjo (ORCPT ); Fri, 6 Jul 2018 01:39:44 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 565DCAD37; Fri, 6 Jul 2018 05:39:43 +0000 (UTC) Date: Fri, 6 Jul 2018 07:39:42 +0200 From: Michal Hocko To: "Paul E. McKenney" Cc: Tetsuo Handa , David Rientjes , linux-mm@kvack.org, Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm,oom: Bring OOM notifier callbacks to outside of OOM killer. Message-ID: <20180706053942.GF32658@dhcp22.suse.cz> References: <20180627143125.GW3593@linux.vnet.ibm.com> <20180628113942.GD32348@dhcp22.suse.cz> <20180628213105.GP3593@linux.vnet.ibm.com> <20180629090419.GD13860@dhcp22.suse.cz> <20180629125218.GX3593@linux.vnet.ibm.com> <20180629132638.GD5963@dhcp22.suse.cz> <20180630170522.GZ3593@linux.vnet.ibm.com> <20180702213714.GA7604@linux.vnet.ibm.com> <20180703072413.GD16767@dhcp22.suse.cz> <20180703160101.GC3593@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180703160101.GC3593@linux.vnet.ibm.com> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 03-07-18 09:01:01, Paul E. McKenney wrote: > On Tue, Jul 03, 2018 at 09:24:13AM +0200, Michal Hocko wrote: > > On Mon 02-07-18 14:37:14, Paul E. McKenney wrote: > > [...] > > > commit d2b8d16b97ac2859919713b2d98b8a3ad22943a2 > > > Author: Paul E. McKenney > > > Date: Mon Jul 2 14:30:37 2018 -0700 > > > > > > rcu: Remove OOM code > > > > > > There is reason to believe that RCU's OOM code isn't really helping > > > that much, given that the best it can hope to do is accelerate invoking > > > callbacks by a few seconds, and even then only if some CPUs have no > > > non-lazy callbacks, a condition that has been observed to be rare. > > > This commit therefore removes RCU's OOM code. If this causes problems, > > > it can easily be reinserted. > > > > > > Reported-by: Michal Hocko > > > Reported-by: Tetsuo Handa > > > Signed-off-by: Paul E. McKenney > > > > I would also note that waiting in the notifier might be a problem on its > > own because we are holding the oom_lock and the system cannot trigger > > the OOM killer while we are holding it and waiting for oom_callback_wq > > event. I am not familiar with the code to tell whether this can deadlock > > but from a quick glance I _suspect_ that we might depend on __rcu_reclaim > > and basically an arbitrary callback so no good. > > > > Acked-by: Michal Hocko > > > > Thanks! > > Like this? Thanks! -- Michal Hocko SUSE Labs