From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, linux-nvdimm@ml01.01.org,
Vishal Verma <vishal.l.verma@intel.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/4] ext4: DAX fixes
Date: Fri, 13 May 2016 01:24:19 -0400 [thread overview]
Message-ID: <20160513052419.GD5862@thunk.org> (raw)
In-Reply-To: <1462959551-28622-1-git-send-email-jack@suse.cz>
On Wed, May 11, 2016 at 11:39:07AM +0200, Jan Kara wrote:
> Hi!
>
> These are ext4 patches that were originally part of my DAX locking patch
> series. They stand on their own so I'm submitting them independently and since
> they are non-trivial, I'd like them to be merged through ext4 tree. The rest
> of the DAX locking series depends on these patches so whichever tree is going
> to merge them will have to pull the ext4 tree to get these patches. They
> didn't change since the last posting of the DAX locking series (except for
> minor fixup due to patch reordering).
>
> Ted, can you please queue these patches for the coming merge window? Thanks!
Queued and I'm running tests before I push them out. The patches
passed the smoke tests[1], and the full tests should be running for the
next seven hours or so at: http://104.197.222.91
I'm also doing a DAX run which should done in a half an hour or so.
- Ted
[1] CMDLINE: smoke
FSTESTVER: e2fsprogs v1.43-WIP-2015-05-18-64-g2334bd3 (Sat, 5 Sep 2015 22:21:35 -0400)
FSTESTVER: fio fio-2.6-8-ge6989e1 (Thu, 4 Feb 2016 12:09:48 -0700)
FSTESTVER: quota 67fd9cc (Mon, 4 Apr 2016 00:32:39 -0400)
FSTESTVER: xfsprogs v4.3.0 (Mon, 23 Nov 2015 15:24:24 +1100)
FSTESTVER: xfstests-bld ccae8d1 (Tue, 26 Apr 2016 00:42:18 -0400)
FSTESTVER: xfstests linux-v3.8-1010-g97dd2d8 (Wed, 27 Apr 2016 00:04:44 -0400)
FSTESTVER: kernel 4.6.0-rc4-ext4-00022-gaacd0c8 #282 SMP Fri May 13 00:52:07 EDT 2016 x86_64
FSTESTCFG: "4k"
FSTESTSET: "-g quick"
FSTESTEXC: ""
FSTESTOPT: "aex"
MNTOPTS: ""
CPUS: "2"
MEM: "7497.07"
MEM: 7680 MB (Max capacity)
BEGIN TEST 4k: Ext4 4k block Fri May 13 01:05:52 EDT 2016
Passed all 158 tests
next prev parent reply other threads:[~2016-05-13 5:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 9:39 [PATCH 0/4] ext4: DAX fixes Jan Kara
2016-05-11 9:39 ` [PATCH 1/4] ext4: Handle transient ENOSPC properly for DAX Jan Kara
2016-05-11 9:39 ` [PATCH 2/4] ext4: Fix race in transient ENOSPC detection Jan Kara
2016-05-11 9:39 ` [PATCH 3/4] ext4: Refactor direct IO code Jan Kara
2016-05-11 9:39 ` [PATCH 4/4] ext4: Pre-zero allocated blocks for DAX IO Jan Kara
2016-05-13 5:24 ` Theodore Ts'o [this message]
2016-05-13 13:56 ` [PATCH 0/4] ext4: DAX fixes Theodore Ts'o
2016-05-16 9:35 ` Jan Kara
2016-05-16 14:26 ` Jan Kara
2016-05-16 15:08 ` Theodore Ts'o
2016-05-16 15:13 ` Dan Williams
2016-05-16 15:59 ` Jan Kara
2016-05-16 18:29 ` Dan Williams
2016-05-16 20:47 ` Theodore Ts'o
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=20160513052419.GD5862@thunk.org \
--to=tytso@mit.edu \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=vishal.l.verma@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).