From: Prakash Sangappa <prakash.sangappa@oracle.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Hansen <dave.hansen@intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: [PATCH RFC] hugetlbfs 'noautofill' mount option
Date: Tue, 27 Jun 2017 13:57:48 -0700 [thread overview]
Message-ID: <b769dc7b-2486-b703-6346-1f80a092cc3f@oracle.com> (raw)
In-Reply-To: <47ea78b4-3b14-264e-2c92-e5e507fd3cba@oracle.com>
On 6/20/17 4:35 PM, Prakash Sangappa wrote:
>
>
> On 6/16/17 6:15 AM, Andrea Arcangeli wrote:
>> Adding a single if (ctx->feature & UFFD_FEATURE_SIGBUS) goto out,
>> branch for this corner case to handle_userfault() isn't great and the
>> hugetlbfs mount option is absolutely zero cost to the handle_userfault
>> which is primarily why I'm not against it.. although it's not going to
>> be measurable so it would be ok also to add such feature.
>
>
> If implementing UFFD_FEATURE_SIGBUS is preferred instead of the mount
> option, I could look into that.
>
Implementing UFFD_FEATURE_SIGBUS seems reasonable.
I wanted to note here on this thread that I sent out a seperate
RFC patch review for adding UFFD_FEATURE_SIGBUS.
See,
http://marc.info/?l=linux-mm&m=149857975906880&w=2
prev parent reply other threads:[~2017-06-27 20:58 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
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 [this message]
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=b769dc7b-2486-b703-6346-1f80a092cc3f@oracle.com \
--to=prakash.sangappa@oracle.com \
--cc=aarcange@redhat.com \
--cc=dave.hansen@intel.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rppt@linux.vnet.ibm.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).