From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: linux-xfs <linux-xfs@vger.kernel.org>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
fstests <fstests@vger.kernel.org>, Jan Kara <jack@suse.cz>,
Dave Chinner <david@fromorbit.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: [xfsprogs PATCH 0/2] Add necessary items for MAP_SYNC testing
Date: Fri, 17 Nov 2017 13:25:22 -0700 [thread overview]
Message-ID: <20171117202524.24696-1-ross.zwisler@linux.intel.com> (raw)
As suggested by Dave Chinner:
As I say to all these sorts of one-off test prgrams: please add the
new MAP_SYNC flag to xfs_io rather than writing a one-off
test program to set it and write some data.
And if we're going to be adding special custom tests just because
we need to insert dm-log marks, add that functionality to xfs_io,
too.
That way we can create complex custom dm logwrite tests without
needing one-off test programs for them all...
This series enhances xfs_io by adding support for the MAP_SYNC mmap() flag
and for dm-log-writes marks. This allows the resulting xfstest for
MAP_SYNC to be much simpler and have no custom C programs.
You can find an xfsprogs branch with this series here:
https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/xfsprogs-dev.git/log/?h=map_sync
Both MAP_SYNC and the DAX enhancements for dm-log-writes will be found in
the upcoming v4.15-rc1. For ease of testing I've posted a kernel that is
v4.14 plus just those two patch series here:
https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/linux.git/log/?h=map_sync_dm_log_writes
Ross Zwisler (2):
xfs_io: add MAP_SYNC support to mmap()
xfs_io: add a new 'log_writes' command
configure.ac | 1 +
include/builddefs.in | 1 +
include/linux.h | 5 ++++
io/Makefile | 5 ++--
io/init.c | 1 +
io/io.h | 2 ++
io/log_writes.c | 78 +++++++++++++++++++++++++++++++++++++++++++++++++++
io/mmap.c | 19 +++++++++----
m4/package_libcdev.m4 | 16 +++++++++++
man/man8/xfs_io.8 | 25 ++++++++++++++++-
10 files changed, 145 insertions(+), 8 deletions(-)
create mode 100644 io/log_writes.c
--
2.9.5
next reply other threads:[~2017-11-17 20:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 20:25 Ross Zwisler [this message]
2017-11-17 20:25 ` [xfsprogs PATCH 1/2] xfs_io: add MAP_SYNC support to mmap() Ross Zwisler
2017-11-17 20:35 ` Dan Williams
2017-11-17 21:33 ` Ross Zwisler
2017-11-17 20:40 ` Darrick J. Wong
2017-11-17 21:44 ` Ross Zwisler
2017-11-17 20:25 ` [xfsprogs PATCH 2/2] xfs_io: add a new 'log_writes' command Ross Zwisler
2017-11-17 20:39 ` Eric Sandeen
2017-11-17 20:48 ` Ross Zwisler
2017-11-17 21:03 ` Eric Sandeen
2017-11-17 21:14 ` Ross Zwisler
2017-11-18 4:44 ` Eric Sandeen
2017-11-17 20:44 ` Darrick J. Wong
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=20171117202524.24696-1-ross.zwisler@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.cz \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.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).