From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx117.postini.com [74.125.245.117]) by kanga.kvack.org (Postfix) with SMTP id 7EBE66B004D for ; Tue, 13 Nov 2012 05:07:41 -0500 (EST) Received: by mail-ee0-f41.google.com with SMTP id c4so4807735eek.14 for ; Tue, 13 Nov 2012 02:07:40 -0800 (PST) Date: Tue, 13 Nov 2012 11:07:36 +0100 From: Ingo Molnar Subject: Re: [PATCH 06/19] mm: numa: teach gup_fast about pmd_numa Message-ID: <20121113100735.GC21522@gmail.com> References: <1352193295-26815-1-git-send-email-mgorman@suse.de> <1352193295-26815-7-git-send-email-mgorman@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1352193295-26815-7-git-send-email-mgorman@suse.de> Sender: owner-linux-mm@kvack.org List-ID: To: Mel Gorman Cc: Peter Zijlstra , Andrea Arcangeli , Rik van Riel , Johannes Weiner , Hugh Dickins , Thomas Gleixner , Linus Torvalds , Andrew Morton , Linux-MM , LKML * Mel Gorman wrote: > From: Andrea Arcangeli > > When scanning pmds, the pmd may be of numa type (_PAGE_PRESENT not set), > however the pte might be present. Therefore, gup_pmd_range() must return > 0 in this case to avoid losing a NUMA hinting page fault during gup_fast. > > Note: gup_fast will skip over non present ptes (like numa > types), so no explicit check is needed for the pte_numa case. > [...] So, why not fix all architectures that choose to expose pte_numa() and pmd_numa() methods - via the patch below? Thanks, Ingo ----------------->