From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751521AbdEBVcs (ORCPT ); Tue, 2 May 2017 17:32:48 -0400 Received: from mga02.intel.com ([134.134.136.20]:23522 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751472AbdEBVcn (ORCPT ); Tue, 2 May 2017 17:32:43 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,281,1491289200"; d="scan'208";a="82999793" Subject: Re: [PATCH RFC] hugetlbfs 'noautofill' mount option To: Prakash Sangappa , linux-kernel@vger.kernel.org, linux-mm@kvack.org References: <326e38dd-b4a8-e0ca-6ff7-af60e8045c74@oracle.com> From: Dave Hansen Message-ID: <7ff6fb32-7d16-af4f-d9d5-698ab7e9e14b@intel.com> Date: Tue, 2 May 2017 14:32:42 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/01/2017 11:00 AM, Prakash Sangappa wrote: > This patch adds a new hugetlbfs mount option 'noautofill', to indicate that > pages should not be allocated at page fault time when accessed thru mmapped > address. I think the main argument against doing something like this is further specializing hugetlbfs. I was really hoping that userfaultfd would be usable for your needs here. Could you elaborate on other options that you considered? Did you look at userfaultfd? What about an madvise() option that disallows backing allocations?