Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755459AbaAVVqN (ORCPT ); Wed, 22 Jan 2014 16:46:13 -0500 Received: from mail-yh0-f42.google.com ([209.85.213.42]:64660 "EHLO mail-yh0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752310AbaAVVqL (ORCPT ); Wed, 22 Jan 2014 16:46:11 -0500 Date: Wed, 22 Jan 2014 13:46:04 -0800 (PST) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Alex Thorlton cc: Mel Gorman , Peter Zijlstra , "Kirill A. Shutemov" , linux-mm@kvack.org, Ingo Molnar , Andrew Morton , "Kirill A. Shutemov" , Benjamin Herrenschmidt , Rik van Riel , Naoya Horiguchi , Oleg Nesterov , "Eric W. Biederman" , Andy Lutomirski , Al Viro , Kees Cook , Andrea Arcangeli , linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] mm: thp: Add per-mm_struct flag to control THP In-Reply-To: <20140122175328.GO18196@sgi.com> Message-ID: References: <1389383718-46031-1-git-send-email-athorlton@sgi.com> <20140110202310.GB1421@node.dhcp.inet.fi> <20140110220155.GD3066@sgi.com> <20140110221010.GP31570@twins.programming.kicks-ass.net> <20140110223909.GA8666@sgi.com> <20140114154457.GD4963@suse.de> <20140114193801.GV10649@sgi.com> <20140122102621.GU4963@suse.de> <20140122175328.GO18196@sgi.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 22 Jan 2014, Alex Thorlton wrote: > > I would expect that the alternative solution to a per-mm switch is to > > reserve the naturally aligned pages for a THP promotion. Have a threshold > > of pages pages that must be faulted before the full THP's worth of pages > > is allocated, zero'd and a huge pmd established. That would defer the > > THP setup costs until it was detected that it was necessary. > > I have some half-finished patches that I was working on a month or so > ago, to do exactly this (I think you were involved with some of the > discussion, maybe? I'd have to dig up the e-mails to be sure). After > cycling through numerous other methods of handling this problem, I still > like that idea, but I think it's going to require a decent amount of > effort to get finished. > If you're going to go this route, I think a sane value would be max_ptes_none that controls when khugepaged would re-collapse a split hugepage into another hugepage after something does madvise(MADV_DONTNEED) to a region, for example. Otherwise it could collapse that memory into a hugepage even though it wasn't faulted as huge. -- 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/