From: Matthew Wilcox <willy@infradead.org>
To: "Luis R. Chamberlain" <mcgrof@kernel.org>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>,
fstests@vger.kernel.org, Amir Goldstein <amir73il@gmail.com>,
Sasha Levin <Alexander.Levin@microsoft.com>,
Sasha Levin <levinsasha928@gmail.com>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: Re: [ANN] oscheck: wrapper for fstests check.sh - tracking and working with baselines
Date: Fri, 13 Jul 2018 13:51:54 -0700 [thread overview]
Message-ID: <20180713205154.GA8782@bombadil.infradead.org> (raw)
In-Reply-To: <CAB=NE6UjcBgQhoQvZoWKXnPWoHVNMbeYdyGfYsHdgeA=L1M4wQ@mail.gmail.com>
On Thu, Jul 12, 2018 at 07:43:08PM -0700, Luis R. Chamberlain wrote:
> Note that while I used this for XFS, it should be easy to add support
> for other filesystems, should folks wish to do something similar for
> their filesystems. The current XFS sections being tested are as
> follows, please let me know if we should consider extending this
> further:
I think we need an xfs_dax section too. It's still ridiculously hard
to set up a DAX test environment though. The best I've been able to
do is now merged into Kent's ktest -- but you're not based on that,
so I'll try and get your ostest set up to work with DAX. Or maybe Ross
can do it since he's actually been able to get 2MB pages working and I
still haven't :-(
next prev parent reply other threads:[~2018-07-13 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 2:43 [ANN] oscheck: wrapper for fstests check.sh - tracking and working with baselines Luis R. Chamberlain
2018-07-13 8:39 ` Amir Goldstein
2018-07-13 16:44 ` Luis R. Chamberlain
2018-07-13 17:46 ` Luis R. Chamberlain
2018-07-13 20:40 ` Jeff Mahoney
2018-07-13 20:50 ` Luis R. Chamberlain
2018-07-13 21:03 ` Jeff Mahoney
2018-07-14 0:52 ` Theodore Y. Ts'o
2018-07-14 6:56 ` Eryu Guan
2018-07-13 20:51 ` Matthew Wilcox [this message]
2018-07-13 20:59 ` Luis R. Chamberlain
2018-07-14 22:21 ` Matthew Wilcox
2018-12-03 23:41 ` Luis Chamberlain
2018-12-04 11:01 ` Kent Overstreet
2019-08-16 17:34 ` Luis Chamberlain
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=20180713205154.GA8782@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=Alexander.Levin@microsoft.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=valentinrothberg@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.