Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752488Ab2KFS4M (ORCPT ); Tue, 6 Nov 2012 13:56:12 -0500 Received: from mx1.redhat.com ([209.132.183.28]:27169 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751158Ab2KFS4L (ORCPT ); Tue, 6 Nov 2012 13:56:11 -0500 Message-ID: <50995DD2.8000200@redhat.com> Date: Tue, 06 Nov 2012 13:58:26 -0500 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121009 Thunderbird/16.0 MIME-Version: 1.0 To: Mel Gorman CC: Peter Zijlstra , Andrea Arcangeli , Ingo Molnar , Johannes Weiner , Hugh Dickins , Thomas Gleixner , Linus Torvalds , Andrew Morton , Linux-MM , LKML Subject: Re: [PATCH 08/19] mm: numa: Create basic numa page hinting infrastructure References: <1352193295-26815-1-git-send-email-mgorman@suse.de> <1352193295-26815-9-git-send-email-mgorman@suse.de> In-Reply-To: <1352193295-26815-9-git-send-email-mgorman@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1706 Lines: 37 On 11/06/2012 04:14 AM, Mel Gorman wrote: > Note: This patch started as "mm/mpol: Create special PROT_NONE > infrastructure" and preserves the basic idea but steals *very* > heavily from "autonuma: numa hinting page faults entry points" for > the actual fault handlers without the migration parts. The end > result is barely recognisable as either patch so all Signed-off > and Reviewed-bys are dropped. If Peter, Ingo and Andrea are ok with > this version, I will re-add the signed-offs-by to reflect the history. > > In order to facilitate a lazy -- fault driven -- migration of pages, create > a special transient PAGE_NUMA variant, we can then use the 'spurious' > protection faults to drive our migrations from. > > Pages that already had an effective PROT_NONE mapping will not be detected The patch itself is good, but the changelog needs a little fix. While you are defining _PAGE_NUMA to _PAGE_PROTNONE on x86, this may be different on other architectures. Therefore, the changelog should refer to PAGE_NUMA, not PROT_NONE. > to generate these 'spurious' faults for the simple reason that we cannot > distinguish them on their protection bits, see pte_numa(). This isn't > a problem since PROT_NONE (and possible PROT_WRITE with dirty tracking) > aren't used or are rare enough for us to not care about their placement. > > Signed-off-by: Mel Gorman Other than the changelog ... Reviewed-by: Rik van Riel -- 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/