Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753608AbbKBKXy (ORCPT ); Mon, 2 Nov 2015 05:23:54 -0500 Received: from mail-wm0-f46.google.com ([74.125.82.46]:36142 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753579AbbKBKXu (ORCPT ); Mon, 2 Nov 2015 05:23:50 -0500 Date: Mon, 2 Nov 2015 10:53:35 +0100 From: Michal Hocko To: "Huang, Ying" Cc: Mel Gorman , lkp@01.org, LKML , Andrew Morton , Rik van Riel , Vitaly Wool , David Rientjes , Christoph Lameter , Johannes Weiner , Vlastimil Babka , Stephen Rothwell Subject: Re: [lkp] [mm, page_alloc] 43993977ba: +88% OOM possibility Message-ID: <20151102095334.GE630@dhcp22.suse.cz> References: <87oafjpnb1.fsf@yhuang-dev.intel.com> <20151029142440.GE23598@dhcp22.suse.cz> <87si4szrzf.fsf@yhuang-dev.intel.com> <20151030103830.GJ18429@dhcp22.suse.cz> <87poztfgsa.fsf@yhuang-dev.intel.com> <20151102074542.GC630@dhcp22.suse.cz> <87twp4232k.fsf@yhuang-dev.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87twp4232k.fsf@yhuang-dev.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1173 Lines: 24 On Mon 02-11-15 16:55:15, Huang, Ying wrote: > Michal Hocko writes: [...] > > It would be interesting to see all the page allocation failure warnings > > (if they are different). Maybe other callers have relied on GFP_ATOMIC > > and access to memory reserves. The above path is not this case though. > > I take a look at all dmesgs, and found the backtrace for page allocation > failure is same for all. Is it possible that this commit cause more > memory were allocated or kept in memory so that more OOM were triggered? I can imagine that some of the callers were not converted properly or missed and a lack of __GFP_KSWAPD_RECLAIM could indeed cause a later kswapd kick off. I am staring into the commit but nothing has jumped at me yet. Could you collect /proc/vmstat (snapshot every 1s) on both good and bad kernels. I expect the later would see a less scanning by kswapd. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/