From: Dan Williams <dan.j.williams@intel.com>
To: willy@bombadil.infradead.org
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
linux-block@vger.kernel.org, Linux MM <linux-mm@kvack.org>
Subject: Re: [LSF/MM TOPIC] Future direction of DAX
Date: Tue, 17 Jan 2017 22:01:30 -0800 [thread overview]
Message-ID: <CAPcyv4jNz=1QdPPtM2A=3avGtVvZG=2d9JC-JD_F6u+-CYQN4g@mail.gmail.com> (raw)
In-Reply-To: <20170118052533.GA18349@bombadil.infradead.org>
On Tue, Jan 17, 2017 at 9:25 PM, <willy@bombadil.infradead.org> wrote:
> On Fri, Jan 13, 2017 at 05:20:08PM -0700, Ross Zwisler wrote:
>> We still have a lot of work to do, though, and I'd like to propose a discussion
>> around what features people would like to see enabled in the coming year as
>> well as what what use cases their customers have that we might not be aware of.
>
> +1 to the discussion
>
>> - Jan suggested [2] that we could use the radix tree as a cache to service DAX
>> faults without needing to call into the filesystem. Are there any issues
>> with this approach, and should we move forward with it as an optimization?
>
> Ahem. I believe I proposed this at last year's LSFMM. And I sent
> patches to start that work. And Dan blocked it. So I'm not terribly
> amused to see somebody else given credit for the idea.
>
I "blocked" moving the phys to virt translation out of the driver
since that mapping lifetime is device specific.
However, I think caching the file offset to physical sector/address
result is a great idea.
--
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-01-18 6:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 0:20 [LSF/MM TOPIC] Future direction of DAX Ross Zwisler
2017-01-14 8:26 ` Darrick J. Wong
2017-01-16 0:19 ` Viacheslav Dubeyko
2017-01-16 20:00 ` Jeff Moyer
2017-01-17 1:50 ` Darrick J. Wong
2017-01-17 2:42 ` Dan Williams
2017-01-17 7:57 ` Christoph Hellwig
2017-01-17 14:54 ` Jeff Moyer
2017-01-17 15:06 ` Christoph Hellwig
2017-01-17 16:07 ` Jeff Moyer
2017-01-17 15:59 ` [Lsf-pc] " Jan Kara
2017-01-17 16:56 ` Dan Williams
2017-01-18 0:03 ` Kani, Toshimitsu
2017-01-18 5:25 ` willy
2017-01-18 6:01 ` Dan Williams [this message]
2017-01-18 6:07 ` willy
2017-01-18 6:25 ` Dan Williams
2017-01-18 17:22 ` 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='CAPcyv4jNz=1QdPPtM2A=3avGtVvZG=2d9JC-JD_F6u+-CYQN4g@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ross.zwisler@linux.intel.com \
--cc=willy@bombadil.infradead.org \
/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).