Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754958AbaGKQY7 (ORCPT ); Fri, 11 Jul 2014 12:24:59 -0400 Received: from mail-qc0-f175.google.com ([209.85.216.175]:34088 "EHLO mail-qc0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754859AbaGKQYz (ORCPT ); Fri, 11 Jul 2014 12:24:55 -0400 Date: Fri, 11 Jul 2014 12:24:51 -0400 From: Tejun Heo To: Christoph Lameter Cc: Jiang Liu , Andrew Morton , Mel Gorman , David Rientjes , Mike Galbraith , Peter Zijlstra , "Rafael J . Wysocki" , Vladimir Davydov , Johannes Weiner , "Kirill A. Shutemov" , Rik van Riel , Wanpeng Li , Zhang Yanfei , Catalin Marinas , Jianyu Zhan , malc , Joonsoo Kim , Fabian Frederick , Tony Luck , linux-mm@kvack.org, linux-hotplug@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC Patch V1 07/30] mm: Use cpu_to_mem()/numa_mem_id() to support memoryless node Message-ID: <20140711162451.GD30865@htj.dyndns.org> References: <1405064267-11678-1-git-send-email-jiang.liu@linux.intel.com> <1405064267-11678-8-git-send-email-jiang.liu@linux.intel.com> <20140711144205.GA27706@htj.dyndns.org> <20140711152156.GB29137@htj.dyndns.org> <20140711160152.GC30865@htj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 11, 2014 at 11:19:14AM -0500, Christoph Lameter wrote: > Yes that works. But if we want a consistent node to allocate from (and > avoid the fallbacks) then we need this patch. I think this is up to those > needing memoryless nodes to figure out what semantics they need. I'm not following what you're saying. Are you saying that we need to spread numa_mem_id() all over the place for GFP_THISNODE users on memless nodes? There aren't that many users of GFP_THISNODE. Wouldn't it make far more sense to just change them? Or just introduce a new GFP flag GFP_CLOSE_OR_BUST which allows falling back to the nearest local node for memless nodes. There's no reason to leak this information outside allocator proper. Thanks. -- tejun -- 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/