linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.com>,
	Matthew Wilcox <willy@linux.intel.com>,
	linux-fsdevel@vger.kernel.org, linux-nvdimm@ml01.01.org
Subject: Re: [PATCH] dax: integrate *sync code & multi-order radix tree
Date: Fri, 15 Apr 2016 14:10:58 -0600	[thread overview]
Message-ID: <20160415201058.GA20412@linux.intel.com> (raw)
In-Reply-To: <1460667804-21725-1-git-send-email-ross.zwisler@linux.intel.com>

On Thu, Apr 14, 2016 at 03:03:24PM -0600, Ross Zwisler wrote:
> With the new addition of the multi-order radix tree support we can simplify
> the DAX *sync PMD support a bit.  Instead of manually checking to see if
> our index is covered by a PMD entry we can rely on the new radix tree to
> return the PMD entry if present.
> 
> Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>

Sorry, I should have explicitly called out that this patch (indeed, all
multi-order uses of the radix tree) need to be built upon the recent
multi-order fixes from Matthew and me:

https://lkml.org/lkml/2016/4/14/481

I've posted a working tree here:

https://git.kernel.org/cgit/linux/kernel/git/zwisler/linux.git/log/?h=dax_mo_radix

Thanks,
- Ross

      reply	other threads:[~2016-04-15 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 21:03 [PATCH] dax: integrate *sync code & multi-order radix tree Ross Zwisler
2016-04-15 20:10 ` Ross Zwisler [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=20160415201058.GA20412@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=david@fromorbit.com \
    --cc=jack@suse.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=viro@zeniv.linux.org.uk \
    --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).