From: Vincent Fu <vincentfu@gmail.com>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Cc: Ankit Kumar <ankit.kumar@samsung.com>,
a.manzanares@samsung.com, krish.reddy@samsung.com,
k.jensen@samsung.com, rstenfort@meta.com
Subject: Blog post on protection information for NVMe devices part 2
Date: Tue, 3 Oct 2023 14:29:35 -0400 [thread overview]
Message-ID: <6ce6c3ad-8a95-6bd0-7083-09585646af64@gmail.com> (raw)
Ankit Kumar and I are back again with part 2 of our blog post series
describing protection information for NVMe devices. This one discusses
using fio to exercise these capabilities. Take a look:
https://github.com/vincentkfu/fio-blog/wiki/Fio-end-to-end-data-protection-part-2-fio-support
Comments, corrections, etc are welcome!
Vincent
reply other threads:[~2023-10-03 18:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6ce6c3ad-8a95-6bd0-7083-09585646af64@gmail.com \
--to=vincentfu@gmail.com \
--cc=a.manzanares@samsung.com \
--cc=ankit.kumar@samsung.com \
--cc=fio@vger.kernel.org \
--cc=k.jensen@samsung.com \
--cc=krish.reddy@samsung.com \
--cc=rstenfort@meta.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).