From: Eryu Guan <eguan@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] dio: reduce the number of cycles
Date: Thu, 15 Jun 2017 14:54:30 +0800 [thread overview]
Message-ID: <20170615065430.GE17436@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170614134939.GB7604@rei.suse.de>
On Wed, Jun 14, 2017 at 03:49:39PM +0200, Cyril Hrubis wrote:
> Hi!
> > I tested diotest30 with 100 iterations and it still could reproduce the
> > bug I was seeing on 4.10 kernel quite reliably (even if not 100%), so
> >
> > Acked-by: Eryu Guan <eguan@redhat.com>
>
> What's the reliability after the patch btw? What is the actual
> percentage of undetected failures for at least 10 runs of the test?
I ran diotest30 10 times with "-i 100" and 8 of them failed. IIRC, it
was not 100% reproduced either when I first saw the test failure in
4.10-rc kernel testing. So I think ~80% probability to reproduce is
fine.
Thanks,
Eryu
next prev parent reply other threads:[~2017-06-15 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 3:38 [LTP] [PATCH] dio: reduce the number of cycles Li Wang
2017-06-14 11:16 ` Eryu Guan
2017-06-14 13:49 ` Cyril Hrubis
2017-06-15 6:54 ` Eryu Guan [this message]
2017-06-15 9:23 ` Cyril Hrubis
2017-06-15 9:38 ` Li Wang
2017-06-15 13:17 ` Cyril Hrubis
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=20170615065430.GE17436@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=ltp@lists.linux.it \
/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