From: Linda Knippers <linda.knippers@hpe.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] test: add fio test for device-dax
Date: Thu, 30 Mar 2017 13:19:47 -0400 [thread overview]
Message-ID: <58DD3E33.2020300@hpe.com> (raw)
In-Reply-To: <CAPcyv4iHJ62Q5bV5UtJSrxfEjN0bGCnV+jYWfuYGrFUnSFQxgg@mail.gmail.com>
On 03/30/2017 01:12 PM, Dan Williams wrote:
> On Thu, Mar 30, 2017 at 10:06 AM, Linda Knippers <linda.knippers@hpe.com> wrote:
>>
>>
>> On 3/30/2017 12:56 PM, Dan Williams wrote:
> [..]
>>> Patches welcome :).
>>
>>
>> You won't like my patch for that because I agree with Jeff. :-)
>>
>> Right now I'm more interested in seeing if I can modify the tests to not
>> require nfit_test. I've only looked at btt-check.sh but so far, it doesn't
>> look that hard.
>
> The point of nfit_test is that you can run them with worrying about
> risks to real data. So I don't want to see patches moving existing
> nfit_test tests to something else.
I'd like to test on an unmodified kernel using real hardware with a real nfit.
As long as it's clear that the test needs a scratch device, why is that bad?
Maybe other tests are more difficult but the btt-check test looks pretty
straightforward.
-- ljk
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2017-03-30 17:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 4:03 [PATCH] test: add fio test for device-dax Dan Williams
2017-03-29 20:02 ` Jeff Moyer
2017-03-29 20:07 ` Dan Williams
2017-03-29 20:19 ` Jeff Moyer
2017-03-29 20:30 ` Dan Williams
2017-03-29 20:49 ` Jeff Moyer
2017-03-29 20:56 ` Dan Williams
2017-03-29 21:04 ` Jeff Moyer
2017-03-29 21:12 ` Dan Williams
2017-03-30 6:16 ` Xiong Zhou
2017-03-30 8:09 ` Eryu Guan
2017-03-31 15:50 ` Dan Williams
2017-03-30 8:47 ` Johannes Thumshirn
2017-03-30 16:08 ` Linda Knippers
2017-03-30 16:56 ` Dan Williams
2017-03-30 17:06 ` Linda Knippers
2017-03-30 17:12 ` Dan Williams
2017-03-30 17:19 ` Linda Knippers [this message]
2017-03-30 17:59 ` Dan Williams
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=58DD3E33.2020300@hpe.com \
--to=linda.knippers@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.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