From: Dan Williams <dan.j.williams@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-block@vger.kernel.org,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Future direction of DAX
Date: Tue, 17 Jan 2017 08:56:52 -0800 [thread overview]
Message-ID: <CAPcyv4hO5ZjrBk=L1DLkf4SP5fFeTAD+o7GUQDv0fcJj4Q+pCg@mail.gmail.com> (raw)
In-Reply-To: <20170117155910.GU2517@quack2.suse.cz>
On Tue, Jan 17, 2017 at 7:59 AM, Jan Kara <jack@suse.cz> wrote:
> On Fri 13-01-17 17:20:08, Ross Zwisler wrote:
>> - The DAX fsync/msync model was built for platforms that need to flush dirty
>> processor cache lines in order to make data durable on NVDIMMs. There exist
>> platforms, however, that are set up so that the processor caches are
>> effectively part of the ADR safe zone. This means that dirty data can be
>> assumed to be durable even in the processor cache, obviating the need to
>> manually flush the cache during fsync/msync. These platforms still need to
>> call fsync/msync to ensure that filesystem metadata updates are properly
>> written to media. Our first idea on how to properly support these platforms
>> would be for DAX to be made aware that in some cases doesn't need to keep
>> metadata about dirty cache lines. A similar issue exists for volatile uses
>> of DAX such as with BRD or with PMEM and the memmap command line parameter,
>> and we'd like a solution that covers them all.
>
> Well, we still need the radix tree entries for locking. And you still need
> to keep track of which file offsets are writeably mapped (which we
> currently implicitely keep via dirty radix tree entries) so that you can
> writeprotect them if needed (during filesystem freezing, for reflink, ...).
> So I think what is going to gain the most by far is simply to avoid doing
> the writeback at all in such situations.
I came to the same conclusion when taking a look at this. I have some
patches that simply make the writeback optional, but do not touch any
of the other dirty tracking infrastructure. I'll send them out shortly
after a bit more testing. This also dovetails with the request from
Linus to push pmem flushing routines into the driver and stop abusing
__copy_user_nocache.
--
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-17 16:56 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 [this message]
2017-01-18 0:03 ` Kani, Toshimitsu
2017-01-18 5:25 ` willy
2017-01-18 6:01 ` Dan Williams
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='CAPcyv4hO5ZjrBk=L1DLkf4SP5fFeTAD+o7GUQDv0fcJj4Q+pCg@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--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 \
/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).