From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-mm@kvack.org, willy@linux.intel.com, ross.zwisler@linux.intel.com
Subject: Re: [PATCH 1/2] dax: rename dax_radix_entry to dax_radix_entry_insert
Date: Thu, 11 Feb 2016 10:42:55 -0700 [thread overview]
Message-ID: <20160211174255.GA11014@linux.intel.com> (raw)
In-Reply-To: <1454939598-16238-1-git-send-email-dmonakhov@openvz.org>
On Mon, Feb 08, 2016 at 05:53:17PM +0400, Dmitry Monakhov wrote:
> - dax_radix_entry_insert is more appropriate name for that function
I think I may have actually had it named that at some point. :) I changed it
because it doesn't always insert an entry - in the read case for example we
insert a clean entry, and then on the following dax_pfn_mkwrite() we call back
in and mark it as dirty.
> - Add lockless helper __dax_radix_entry_insert, it will be used by second patch
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> ---
> fs/dax.c | 39 +++++++++++++++++++++++----------------
> 1 file changed, 23 insertions(+), 16 deletions(-)
>
> diff --git a/fs/dax.c b/fs/dax.c
> index fc2e314..89bb1f8 100644
> --- a/fs/dax.c
> +++ b/fs/dax.c
<>
> @@ -579,8 +586,8 @@ static int dax_insert_mapping(struct inode *inode, struct buffer_head *bh,
> }
> dax_unmap_atomic(bdev, &dax);
>
> - error = dax_radix_entry(mapping, vmf->pgoff, dax.sector, false,
> - vmf->flags & FAULT_FLAG_WRITE);
> + error = dax_radix_entry_insert(mapping, vmf->pgoff, dax.sector, false,
> + vmf->flags & FAULT_FLAG_WRITE, vmf->page);
fs/dax.c: In function a??dax_insert_mappinga??:
fs/dax.c:589:10: error: too many arguments to function a??dax_radix_entry_inserta??
error = dax_radix_entry_insert(mapping, vmf->pgoff, dax.sector, false,
^
fs/dax.c:415:12: note: declared here
static int dax_radix_entry_insert(struct address_space *mapping, pgoff_t index,
^
scripts/Makefile.build:258: recipe for target 'fs/dax.o' failed
--
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:[~2016-02-11 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 11:23 DAX: __dax_fault race question Dmitry Monakhov
2016-02-08 13:53 ` [PATCH 1/2] dax: rename dax_radix_entry to dax_radix_entry_insert Dmitry Monakhov
2016-02-08 13:53 ` [PATCH 2/2] dax: fix race dax_fault write vs read Dmitry Monakhov
2016-02-11 17:42 ` Ross Zwisler [this message]
2016-02-11 18:43 ` DAX: __dax_fault race question Ross Zwisler
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=20160211174255.GA11014@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=dmonakhov@openvz.org \
--cc=linux-mm@kvack.org \
--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 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).