From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Subject: Re: [PATCHv3 1/2] mm: introduce vm_ops->map_pages() Date: Thu, 27 Feb 2014 13:59:59 -0800 Message-ID: <530FB55F.2070106@linux.intel.com> References: <1393530827-25450-1-git-send-email-kirill.shutemov@linux.intel.com> <1393530827-25450-2-git-send-email-kirill.shutemov@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Andi Kleen , Matthew Wilcox , Alexander Viro , Dave Chinner , Ning Qu , linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: "Kirill A. Shutemov" , Linus Torvalds , Andrew Morton , Mel Gorman , Rik van Riel Return-path: In-Reply-To: <1393530827-25450-2-git-send-email-kirill.shutemov@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 02/27/2014 11:53 AM, Kirill A. Shutemov wrote: > +#define FAULT_AROUND_ORDER 4 > +#define FAULT_AROUND_PAGES (1UL << FAULT_AROUND_ORDER) > +#define FAULT_AROUND_MASK ~((1UL << (PAGE_SHIFT + FAULT_AROUND_ORDER)) - 1) Looking at the performance data made me think of this: do we really want this to be static? It seems like the kind of thing that will cause a regression _somewhere_. Also, the folks with larger base bage sizes probably don't want a FAULT_AROUND_ORDER=4. That's 1MB of fault-around for ppc64, for example.