From: Jan Kara <jack@suse.cz>
To: Matthew Wilcox <matthew.r.wilcox@intel.com>
Cc: Jan Kara <jack@suse.cz>, Dave Chinner <david@fromorbit.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Matthew Wilcox <willy@linux.intel.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm,fs,dax: Change ->pmd_fault to ->huge_fault
Date: Thu, 28 Jan 2016 13:17:10 +0100 [thread overview]
Message-ID: <20160128121710.GF7726@quack.suse.cz> (raw)
In-Reply-To: <1453867708-3999-2-git-send-email-matthew.r.wilcox@intel.com>
On Tue 26-01-16 23:08:27, Matthew Wilcox wrote:
> From: Matthew Wilcox <willy@linux.intel.com>
>
> In preparation for adding the ability to handle PUD pages, convert
> ->pmd_fault to ->huge_fault. huge_fault() takes a vm_fault structure
> instead of separate (address, pmd, flags) parameters. The vm_fault
> structure is extended to include a union of the different page table
> pointers that may be needed, and three flag bits are reserved to indicate
> which type of pointer is in the union.
>
> The DAX fault handlers are unified into one entry point, meaning that
> the filesystems can be largely unconcerned with what size of fault they
> are handling. ext4 needs to know in order to reserve enough blocks in
> the journal, but ext2 and xfs are oblivious.
>
> The existing dax_fault and dax_mkwrite had no callers, so rename the
> __dax_fault and __dax_mkwrite to lose the initial underscores.
>
> Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
Thanks for these simplifications. I like them! Just one nit below:
> diff --git a/mm/memory.c b/mm/memory.c
> index a2eaeef..03d49eb 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -3274,10 +3274,16 @@ out:
> static int create_huge_pmd(struct mm_struct *mm, struct vm_area_struct *vma,
> unsigned long address, pmd_t *pmd, unsigned int flags)
> {
> + struct vm_fault vmf = {
> + .virtual_address = (void __user *)address,
> + .flags = flags | FAULT_FLAG_SIZE_PMD,
> + .pmd = pmd,
> + };
> +
I think we should fill in also the vmf.gfp_mask and vmf.pgoff fields. I
know they are not currently used but it would be a nasty surprise if
someone tried to use them in the future...
Otherwise feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-01-28 12:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 4:08 [PATCH 0/2] Fix dax races between page faults RFC only Matthew Wilcox
2016-01-27 4:08 ` [PATCH 1/2] mm,fs,dax: Change ->pmd_fault to ->huge_fault Matthew Wilcox
2016-01-27 5:48 ` kbuild test robot
2016-01-27 17:47 ` Ross Zwisler
2016-01-28 12:17 ` Jan Kara [this message]
2016-01-29 14:31 ` Matthew Wilcox
2016-01-27 4:08 ` [PATCH 2/2] dax: Giant hack Matthew Wilcox
2016-01-28 13:10 ` Jan Kara
2016-01-28 21:23 ` Dave Chinner
2016-01-29 22:29 ` Jared Hulbert
[not found] ` <CAOxpaSU_JgkeS=u61zxWTdP5hXymBkUsvkjkwNzm6XVig9y8RQ@mail.gmail.com>
2016-01-27 6:18 ` [PATCH 0/2] Fix dax races between page faults RFC only Matthew Wilcox
2016-02-01 21:25 ` Ross Zwisler
2016-01-28 12:48 ` 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=20160128121710.GF7726@quack.suse.cz \
--to=jack@suse.cz \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew.r.wilcox@intel.com \
--cc=ross.zwisler@linux.intel.com \
--cc=willy@linux.intel.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 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.