From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754203AbbCBPqh (ORCPT ); Mon, 2 Mar 2015 10:46:37 -0500 Received: from resqmta-ch2-08v.sys.comcast.net ([69.252.207.40]:37954 "EHLO resqmta-ch2-08v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753613AbbCBPqf (ORCPT ); Mon, 2 Mar 2015 10:46:35 -0500 Date: Mon, 2 Mar 2015 09:46:33 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: Vlastimil Babka cc: David Rientjes , Andrew Morton , Pekka Enberg , Joonsoo Kim , Johannes Weiner , Mel Gorman , Pravin Shelar , Jarno Rajahalme , Li Zefan , Greg Thelen , linux-kernel@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org, cgroups@vger.kernel.org, dev@openvswitch.org Subject: Re: [patch v2 1/3] mm: remove GFP_THISNODE In-Reply-To: <54F469C1.9090601@suse.cz> Message-ID: References: <54F469C1.9090601@suse.cz> 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 Mon, 2 Mar 2015, Vlastimil Babka wrote: > So it would be IMHO better for longer-term maintainability to have the > relevant __GFP_THISNODE callers pass also __GFP_NO_KSWAPD to denote these > opportunistic allocation attempts, instead of having this subtle semantic You are thinking about an opportunistic allocation attempt in SLAB? AFAICT SLAB allocations should trigger reclaim.