From: Dave Hansen <dave.hansen@intel.com>
To: Prakash Sangappa <prakash.sangappa@oracle.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH RFC] hugetlbfs 'noautofill' mount option
Date: Tue, 2 May 2017 14:32:42 -0700 [thread overview]
Message-ID: <7ff6fb32-7d16-af4f-d9d5-698ab7e9e14b@intel.com> (raw)
In-Reply-To: <b0efc671-0d7a-0aef-5646-a635478c31b0@oracle.com>
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?
next prev parent reply other threads:[~2017-05-02 21:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <326e38dd-b4a8-e0ca-6ff7-af60e8045c74@oracle.com>
2017-05-01 18:00 ` [PATCH RFC] hugetlbfs 'noautofill' mount option Prakash Sangappa
2017-05-02 10:53 ` Anshuman Khandual
2017-05-02 16:07 ` Prakash Sangappa
2017-05-02 21:32 ` Dave Hansen [this message]
2017-05-02 23:34 ` Prakash Sangappa
2017-05-02 23:43 ` Dave Hansen
2017-05-03 19:02 ` Prakash Sangappa
2017-05-08 5:57 ` Prakash Sangappa
2017-05-08 15:58 ` Dave Hansen
2017-05-08 22:12 ` prakash.sangappa
2017-05-09 8:58 ` Christoph Hellwig
2017-05-09 20:59 ` Prakash Sangappa
2017-05-16 16:51 ` Prakash Sangappa
2017-06-16 13:15 ` Andrea Arcangeli
2017-06-20 23:35 ` Prakash Sangappa
2017-06-27 20:57 ` Prakash Sangappa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ff6fb32-7d16-af4f-d9d5-698ab7e9e14b@intel.com \
--to=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=prakash.sangappa@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).