From: Dave Chinner <david@fromorbit.com>
To: Jan Kara <jack@suse.cz>
Cc: Ted Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: Re: [PATCH 0/11 v2] ext4: Convert ext4 DAX IO to iomap framework
Date: Wed, 9 Nov 2016 10:17:39 +1100 [thread overview]
Message-ID: <20161108231739.GQ28177@dastard> (raw)
In-Reply-To: <1478603297-11793-1-git-send-email-jack@suse.cz>
On Tue, Nov 08, 2016 at 12:08:06PM +0100, Jan Kara wrote:
> Hello,
>
> this is a second revision of my patches to convert ext4 DAX IO paths to the new
> iomap framework and removes the old bh-based DAX functions. As a result ext4
> gains PMD page fault support, also some other minor bugs get fixed. The patch
> set is based on Ross' DAX PMD page fault support series [1]. It passes xfstests
> both in DAX and non-DAX mode.
>
> I have pushed out updated version of these patches including the follow-up
> DAX patches to:
>
> git://get.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git dax
>
> for easy testing. Once Dave pushes out a stable branch with Ross' patches, we
> pull those into ext4 tree and then pull these patches on top of that (provided
> nobody will have other objections to the current series).
Done:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git dax-4.10-iomap-pmd
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-11-08 23:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 11:08 [PATCH 0/11 v2] ext4: Convert ext4 DAX IO to iomap framework Jan Kara
2016-11-08 11:08 ` [PATCH 01/11] ext4: Factor out checks from ext4_file_write_iter() Jan Kara
2016-11-10 21:25 ` Ross Zwisler
2016-11-08 11:08 ` [PATCH 02/11] ext4: Let S_DAX set only if DAX is really supported Jan Kara
2016-11-10 21:46 ` Ross Zwisler
2016-11-11 10:08 ` Jan Kara
2016-11-11 17:56 ` Ross Zwisler
2016-11-08 11:08 ` [PATCH 03/11] ext4: Convert DAX reads to iomap infrastructure Jan Kara
2016-11-10 21:54 ` Ross Zwisler
2016-11-11 10:17 ` Jan Kara
2016-11-11 17:57 ` Ross Zwisler
2016-11-08 11:08 ` [PATCH 04/11] ext4: Use iomap for zeroing blocks in DAX mode Jan Kara
2016-11-10 22:05 ` Ross Zwisler
2016-11-08 11:08 ` [PATCH 05/11] ext4: DAX iomap write support Jan Kara
2016-11-08 11:08 ` [PATCH 06/11] ext4: Avoid split extents for DAX writes Jan Kara
2016-11-11 20:25 ` Ross Zwisler
2016-11-14 8:54 ` Jan Kara
2016-11-08 11:08 ` [PATCH 07/11] dax: Introduce IOMAP_FAULT flag Jan Kara
2016-11-08 23:21 ` Dave Chinner
2016-11-09 15:03 ` Christoph Hellwig
2016-11-08 11:08 ` [PATCH 08/11] ext4: Convert DAX faults to iomap infrastructure Jan Kara
2016-11-08 11:08 ` [PATCH 09/11] ext4: Rip out DAX handling from direct IO path Jan Kara
2016-11-16 17:13 ` Ross Zwisler
2016-11-17 9:41 ` Jan Kara
2016-11-08 11:08 ` [PATCH 10/11] ext2: Use iomap_zero_range() for zeroing truncated page in DAX path Jan Kara
2016-11-16 17:31 ` Ross Zwisler
2016-11-08 11:08 ` [PATCH 11/11] dax: Rip out get_block based IO support Jan Kara
2016-11-16 18:11 ` Ross Zwisler
2016-11-17 9:45 ` Jan Kara
2016-11-08 23:17 ` Dave Chinner [this message]
2016-11-09 15:02 ` [PATCH 0/11 v2] ext4: Convert ext4 DAX IO to iomap framework Christoph Hellwig
2016-11-09 23:22 ` Dave Chinner
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=20161108231739.GQ28177@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
/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).