From: Robert Elliott <elliott@hpe.com>
To: fio@vger.kernel.org
Cc: Robert Elliott <elliott@hpe.com>
Subject: [PATCH v2 2/4] pmemblk, dev-dax: Update descriptions
Date: Tue, 10 Jan 2017 15:21:25 -0600 [thread overview]
Message-ID: <20170110212127.64926-2-elliott@hpe.com> (raw)
In-Reply-To: <20170110212127.64926-1-elliott@hpe.com>
From: Robert Elliott <elliott@hpe.com>
Make the descriptions of the pmemblk and dev-dax ioengines
more symmetric.
---
HOWTO | 10 ++++++----
fio.1 | 6 ++++--
2 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/HOWTO b/HOWTO
index 4354e46..9e1ffa6 100644
--- a/HOWTO
+++ b/HOWTO
@@ -903,11 +903,13 @@ ioengine=str Defines how the job issues io to the file. The following
overwriting. The writetrim mode works well
for this constraint.
- pmemblk Read and write through the NVML libpmemblk
- interface.
+ pmemblk Read and write using filesystem DAX to a file
+ on a filesystem mounted with DAX on a persistent
+ memory device through the NVML libpmemblk library.
- dev-dax Read and write through a DAX device exposed
- from persistent memory.
+ dev-dax Read and write using device DAX to a persistent
+ memory device (e.g., /dev/dax0.0) through the
+ NVML libpmem library.
external Prefix to specify loading an external
IO engine object file. Append the engine
diff --git a/fio.1 b/fio.1
index f486276..56f2d11 100644
--- a/fio.1
+++ b/fio.1
@@ -811,10 +811,12 @@ and discarding before overwriting. The trimwrite mode works well for this
constraint.
.TP
.B pmemblk
-Read and write through the NVML libpmemblk interface.
+Read and write using filesystem DAX to a file on a filesystem mounted with
+DAX on a persistent memory device through the NVML libpmemblk library.
.TP
.B dev-dax
-Read and write through a DAX device exposed from persistent memory.
+Read and write using device DAX to a persistent memory device
+(e.g., /dev/dax0.0) through the NVML libpmem library.
.RE
.P
.RE
--
2.9.3
next prev parent reply other threads:[~2017-01-10 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 6:54 pmemblk and dev-dax cleanups Robert Elliott
2017-01-04 6:54 ` [PATCH 1/4] pmemblk, dev-dax: load libpmem and libpmemblk at startup Robert Elliott
2017-01-04 23:48 ` Elliott, Robert (Persistent Memory)
2017-01-04 6:54 ` [PATCH 2/4] pmemblk, dev-dax: Update descriptions Robert Elliott
2017-01-04 6:54 ` [PATCH 3/4] pmemblk,dev-dax: clean up error logs Robert Elliott
2017-01-04 6:54 ` [PATCH 4/4] pmemblk: Clarify fsize is in MiB not MB Robert Elliott
2017-01-05 18:47 ` pmemblk and dev-dax cleanups Jens Axboe
2017-01-10 21:21 ` [PATCH v2 1/4] pmemblk, dev-dax: load libpmem and libpmemblk at startup Robert Elliott
2017-01-10 21:21 ` Robert Elliott [this message]
2017-01-10 21:21 ` [PATCH v2 3/4] pmemblk, dev-dax: clean up error logs Robert Elliott
2017-01-10 21:21 ` [PATCH v2 4/4] pmemblk: Clarify fsize is in MiB not MB Robert Elliott
2017-01-12 4:00 ` [PATCH v2 1/4] pmemblk, dev-dax: load libpmem and libpmemblk at startup Jens Axboe
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=20170110212127.64926-2-elliott@hpe.com \
--to=elliott@hpe.com \
--cc=fio@vger.kernel.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.