From: E.W.Z. <kreuzerkrieg at gmail.com>
To: spdk@lists.01.org
Subject: [SPDK] Code robustness test
Date: Wed, 07 Feb 2018 18:13:42 +0200 [thread overview]
Message-ID: <5a7b25b5.47a5500a.6027f.9506@mx.google.com> (raw)
In-Reply-To: CA+BiufqzOiFEyrC9SoruAChSBkOnax=4YRyjq=UspgVFu=B33g@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 271 bytes --]
Hi,
Is there anything that can wreck havoc on NVMe to check how well the code copes with it? Something like a script or utility that runs in background and resets PCIe controller, detaches disks and anything else that could theoretically happen to NVMe.
Thanks,
E.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 1573 bytes --]
next reply other threads:[~2018-02-07 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 16:13 E.W.Z. [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-07 23:37 [SPDK] Code robustness test Luse, Paul E
2018-02-08 5:57 Ernest Zaslavsky
2018-02-08 7:12 Szwed, Maciej
2018-02-08 7:14 Ernest Zaslavsky
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=5a7b25b5.47a5500a.6027f.9506@mx.google.com \
--to=spdk@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 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.