From: Mike Snitzer <snitzer@redhat.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Josef Bacik <jbacik@fb.com>,
Alasdair Kergon <agk@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
Shaohua Li <shli@kernel.org>,
dm-devel@redhat.com, linux-nvdimm@lists.01.org,
linux-raid@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 2/2] dm log writes: add support for DAX
Date: Tue, 24 Oct 2017 15:22:23 -0400 [thread overview]
Message-ID: <20171024192222.GB22902@redhat.com> (raw)
In-Reply-To: <20171020052404.13762-2-ross.zwisler@linux.intel.com>
On Fri, Oct 20 2017 at 1:24am -0400,
Ross Zwisler <ross.zwisler@linux.intel.com> wrote:
> Now that we have the ability log filesystem writes using a flat buffer, add
> support for DAX. Unfortunately we can't easily track data that has been
> written via mmap() now that the dax_flush() abstraction was removed by this
> commit:
>
> commit c3ca015fab6d ("dax: remove the pmem_dax_ops->flush abstraction")
>
> Otherwise we could just treat each flush as a big write, and store the data
> that is being synced to media. It may be worthwhile to add the dax_flush()
> entry point back, just as a notifier so we can do this logging.
>
> The motivation for this support is the need for an xfstest that can test
> the new MAP_SYNC DAX flag. By logging the filesystem activity with
> dm-log-writes we can show that the MAP_SYNC page faults are writing out
> their metadata as they happen, instead of requiring an explicit
> msync/fsync.
>
> Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
I've picked this up, please see:
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-4.15/dm&id=ae613bbb0144e84cb3c0ebfa9f4fd4d1507c2f0e
I tweaked the header and tweaked a couple whitespace nits. Also
switched version bump from 1.0.1 to 1.1.0.
Thanks,
Mike
next prev parent reply other threads:[~2017-10-24 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 5:24 [PATCH 1/2] dm log writes: Add support for inline data buffers Ross Zwisler
2017-10-20 5:24 ` [PATCH 2/2] dm log writes: add support for DAX Ross Zwisler
2017-10-23 17:34 ` Josef Bacik
2017-10-23 18:59 ` Ross Zwisler
2017-10-24 19:22 ` Mike Snitzer [this message]
2017-10-24 19:30 ` Ross Zwisler
2017-10-20 5:29 ` [fstests PATCH] generic: add test for DAX MAP_SYNC support Ross Zwisler
2017-10-20 6:51 ` Amir Goldstein
2017-10-20 21:25 ` [fstests PATCH v2] " Ross Zwisler
2017-10-22 6:56 ` Amir Goldstein
2017-10-25 12:19 ` Amir Goldstein
2017-10-25 17:12 ` Ross Zwisler
2017-10-25 20:47 ` [fstests PATCH v3] " Ross Zwisler
2017-10-25 21:56 ` Dave Chinner
2017-11-16 21:28 ` Ross Zwisler
2017-11-16 21:31 ` Ross Zwisler
2017-10-26 4:59 ` Amir Goldstein
2017-11-16 22:59 ` Ross Zwisler
2017-10-24 19:14 ` [PATCH 1/2] dm log writes: Add support for inline data buffers Mike Snitzer
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=20171024192222.GB22902@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=shli@kernel.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).