From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-xfs@vger.kernel.org,
Matthew Wilcox <mawilcox@microsoft.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Christoph Hellwig <hch@infradead.org>,
Linux MM <linux-mm@kvack.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Jan Kara <jack@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm: replace FAULT_FLAG_SIZE with parameter to huge_fault
Date: Mon, 6 Feb 2017 09:27:31 -0800 [thread overview]
Message-ID: <20170206172731.GA17515@infradead.org> (raw)
In-Reply-To: <CAPcyv4jHYR2-_SgD7a6ab5vWigYsDoSb7FZdTchP8Xg+BF-2yg@mail.gmail.com>
On Mon, Feb 06, 2017 at 08:24:48AM -0800, Dan Williams wrote:
> > Also can be use this opportunity
> > to fold ->huge_fault into ->fault?
>
> Hmm, yes, just need a scheme to not attempt huge_faults on pte-only handlers.
Do we need anything more than checking vma->vm_flags for VM_HUGETLB?
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <mawilcox@microsoft.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-xfs@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
Vlastimil Babka <vbabka@suse.cz>, Jan Kara <jack@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] mm: replace FAULT_FLAG_SIZE with parameter to huge_fault
Date: Mon, 6 Feb 2017 09:27:31 -0800 [thread overview]
Message-ID: <20170206172731.GA17515@infradead.org> (raw)
In-Reply-To: <CAPcyv4jHYR2-_SgD7a6ab5vWigYsDoSb7FZdTchP8Xg+BF-2yg@mail.gmail.com>
On Mon, Feb 06, 2017 at 08:24:48AM -0800, Dan Williams wrote:
> > Also can be use this opportunity
> > to fold ->huge_fault into ->fault?
>
> Hmm, yes, just need a scheme to not attempt huge_faults on pte-only handlers.
Do we need anything more than checking vma->vm_flags for VM_HUGETLB?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <mawilcox@microsoft.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-xfs@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
Vlastimil Babka <vbabka@suse.cz>, Jan Kara <jack@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] mm: replace FAULT_FLAG_SIZE with parameter to huge_fault
Date: Mon, 6 Feb 2017 09:27:31 -0800 [thread overview]
Message-ID: <20170206172731.GA17515@infradead.org> (raw)
In-Reply-To: <CAPcyv4jHYR2-_SgD7a6ab5vWigYsDoSb7FZdTchP8Xg+BF-2yg@mail.gmail.com>
On Mon, Feb 06, 2017 at 08:24:48AM -0800, Dan Williams wrote:
> > Also can be use this opportunity
> > to fold ->huge_fault into ->fault?
>
> Hmm, yes, just need a scheme to not attempt huge_faults on pte-only handlers.
Do we need anything more than checking vma->vm_flags for VM_HUGETLB?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-02-06 17:27 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 21:31 [PATCH] mm: replace FAULT_FLAG_SIZE with parameter to huge_fault Dave Jiang
2017-02-03 21:31 ` Dave Jiang
2017-02-03 21:31 ` Dave Jiang
2017-02-03 21:31 ` Dave Jiang
2017-02-03 21:47 ` Dan Williams
2017-02-03 21:47 ` Dan Williams
2017-02-03 21:47 ` Dan Williams
2017-02-03 22:56 ` kbuild test robot
2017-02-03 22:56 ` kbuild test robot
2017-02-03 22:56 ` kbuild test robot
2017-02-03 23:25 ` Dave Jiang
2017-02-03 23:25 ` Dave Jiang
2017-02-03 23:25 ` Dave Jiang
2017-02-03 23:26 ` Dan Williams
2017-02-03 23:26 ` Dan Williams
2017-02-04 0:00 ` Dan Williams
2017-02-04 0:00 ` Dan Williams
2017-02-04 0:00 ` Dan Williams
2017-02-04 0:07 ` Dave Jiang
2017-02-04 0:07 ` Dave Jiang
2017-02-04 0:07 ` Dave Jiang
2017-02-09 4:34 ` [kbuild-all] " Ye Xiaolong
2017-02-09 4:34 ` Ye Xiaolong
2017-02-09 4:34 ` Ye Xiaolong
2017-02-09 4:34 ` Ye Xiaolong
2017-02-04 3:51 ` kbuild test robot
2017-02-04 3:51 ` kbuild test robot
2017-02-04 3:51 ` kbuild test robot
2017-02-06 8:51 ` Jan Kara
2017-02-06 8:51 ` Jan Kara
2017-02-06 8:51 ` Jan Kara
2017-02-06 8:51 ` Jan Kara
2017-02-06 14:36 ` Christoph Hellwig
2017-02-06 14:36 ` Christoph Hellwig
2017-02-06 14:36 ` Christoph Hellwig
2017-02-06 14:36 ` Christoph Hellwig
2017-02-06 16:24 ` Dan Williams
2017-02-06 16:24 ` Dan Williams
2017-02-06 16:24 ` Dan Williams
2017-02-06 17:27 ` Christoph Hellwig [this message]
2017-02-06 17:27 ` Christoph Hellwig
2017-02-06 17:27 ` Christoph Hellwig
2017-02-06 17:30 ` Dan Williams
2017-02-06 17:30 ` Dan Williams
2017-02-06 17:30 ` Dan Williams
2017-02-07 8:44 ` Kirill A. Shutemov
2017-02-07 8:44 ` Kirill A. Shutemov
2017-02-07 8:44 ` Kirill A. Shutemov
2017-02-07 16:56 ` Dan Williams
2017-02-07 16:56 ` Dan Williams
2017-02-07 16:56 ` Dan Williams
2017-02-07 17:40 ` Kirill A. Shutemov
2017-02-07 17:40 ` Kirill A. Shutemov
2017-02-07 17:40 ` Kirill A. Shutemov
2017-02-07 18:08 ` Dan Williams
2017-02-07 18:08 ` Dan Williams
2017-02-07 18:08 ` Dan Williams
2017-02-07 18:08 ` Dan Williams
2017-02-08 8:41 ` Jan Kara
2017-02-08 8:41 ` Jan Kara
2017-02-08 8:41 ` Jan Kara
2017-02-08 8:41 ` Jan Kara
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=20170206172731.GA17515@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jack@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.