From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751255AbeDDGXn (ORCPT ); Wed, 4 Apr 2018 02:23:43 -0400 Received: from mx2.suse.de ([195.135.220.15]:45908 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750711AbeDDGXm (ORCPT ); Wed, 4 Apr 2018 02:23:42 -0400 Date: Wed, 4 Apr 2018 08:23:40 +0200 From: Michal Hocko To: Zhaoyang Huang Cc: Steven Rostedt , Ingo Molnar , linux-kernel@vger.kernel.org, kernel-patch-test@lists.linaro.org, Andrew Morton , Joel Fernandes , linux-mm@kvack.org, Vlastimil Babka Subject: Re: [PATCH v1] kernel/trace:check the val against the available mem Message-ID: <20180404062340.GD6312@dhcp22.suse.cz> References: <1522320104-6573-1-git-send-email-zhaoyang.huang@spreadtrum.com> <20180330102038.2378925b@gandalf.local.home> <20180403110612.GM5501@dhcp22.suse.cz> <20180403075158.0c0a2795@gandalf.local.home> <20180403121614.GV5501@dhcp22.suse.cz> <20180403082348.28cd3c1c@gandalf.local.home> <20180403123514.GX5501@dhcp22.suse.cz> <20180403093245.43e7e77c@gandalf.local.home> <20180403135607.GC5501@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 04-04-18 10:58:39, Zhaoyang Huang wrote: > On Tue, Apr 3, 2018 at 9:56 PM, Michal Hocko wrote: > > On Tue 03-04-18 09:32:45, Steven Rostedt wrote: > >> On Tue, 3 Apr 2018 14:35:14 +0200 > >> Michal Hocko wrote: > > [...] > >> > Being clever is OK if it doesn't add a tricky code. And relying on > >> > si_mem_available is definitely tricky and obscure. > >> > >> Can we get the mm subsystem to provide a better method to know if an > >> allocation will possibly succeed or not before trying it? It doesn't > >> have to be free of races. Just "if I allocate this many pages right > >> now, will it work?" If that changes from the time it asks to the time > >> it allocates, that's fine. I'm not trying to prevent OOM to never > >> trigger. I just don't want to to trigger consistently. > > > > How do you do that without an actuall allocation request? And more > > fundamentally, what if your _particular_ request is just fine but it > > will get us so close to the OOM edge that the next legit allocation > > request simply goes OOM? There is simply no sane interface I can think > > of that would satisfy a safe/sensible "will it cause OOM" semantic. > > > The point is the app which try to allocate the size over the line will escape > the OOM and let other innocent to be sacrificed. However, the one which you > mentioned above will be possibly selected by OOM that triggered by consequnce > failed allocation. If you are afraid of that then you can have a look at {set,clear}_current_oom_origin() which will automatically select the current process as an oom victim and kill it. -- Michal Hocko SUSE Labs