From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751228AbdBATBj (ORCPT ); Wed, 1 Feb 2017 14:01:39 -0500 Received: from mga07.intel.com ([134.134.136.100]:4654 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751092AbdBATBi (ORCPT ); Wed, 1 Feb 2017 14:01:38 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,321,1477983600"; d="scan'208";a="1089774539" Subject: Re: [RFC V2 02/12] mm: Isolate HugeTLB allocations away from CDM nodes To: Anshuman Khandual , linux-kernel@vger.kernel.org, linux-mm@kvack.org References: <20170130033602.12275-1-khandual@linux.vnet.ibm.com> <20170130033602.12275-3-khandual@linux.vnet.ibm.com> <01671749-c649-e015-4f51-7acaa1fb5b80@intel.com> Cc: mhocko@suse.com, vbabka@suse.cz, mgorman@suse.de, minchan@kernel.org, aneesh.kumar@linux.vnet.ibm.com, bsingharora@gmail.com, srikar@linux.vnet.ibm.com, haren@linux.vnet.ibm.com, jglisse@redhat.com, dan.j.williams@intel.com From: Dave Hansen Message-ID: <0f7b1e14-536f-0f2f-5345-90b5bb597a84@intel.com> Date: Wed, 1 Feb 2017 11:01:35 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/01/2017 05:59 AM, Anshuman Khandual wrote: > So shall we write all these details in the comment section for each > patch after the SOB statement to be more visible ? Or some where > in-code documentation as FIXME or XXX or something. These are little > large paragraphs, hence was wondering. I would make an effort to convey a maximum amount of content in a minimal amount of words. :) But, yeah, it is pretty obvious that you've got too much in the cover letter and not enough in the patches descriptions. ... > * Page faults (which will probably use __GFP_THISNODE) cannot come from the > CDM nodes as they dont have any CPUs. Page faults happen on CPUs but they happen on VMAs that could be bound to a CDM node. We allocate based on the VMA policy first, the fall back to the default policy which is based on the CPU doing the fault if the VMA doesn't have a specific policy.