From: Robert Elliott <elliott@hpe.com>
To: fio@vger.kernel.org
Subject: pmemblk and dev-dax cleanups
Date: Wed, 4 Jan 2017 00:54:49 -0600 [thread overview]
Message-ID: <20170104065453.15106-1-elliott@hpe.com> (raw)
This series changes library loading to startup time, and resubmits
pmemblk and dev-dax patches that were not posted earlier but not
included in the previous 12-part series of binary/decimal prefix
cleanups.
[PATCH 1/4] pmemblk, dev-dax: load libpmem and libpmemblk at startup
[PATCH 2/4] pmemblk, dev-dax: Update descriptions
[PATCH 3/4] pmemblk,dev-dax: clean up error logs
[PATCH 4/4] pmemblk: Clarify fsize is in MiB not MB
HOWTO | 10 +++++---
configure | 4 ++-
engines/dev-dax.c | 44 +++++++++-----------------------
engines/pmemblk.c | 117 ++++++++++++++++++++++--------------------------------------------------------------
fio.1 | 6 +++--
5 files changed, 56 insertions(+), 125 deletions(-)
next reply other threads:[~2017-01-04 6:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 6:54 Robert Elliott [this message]
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 ` [PATCH v2 2/4] pmemblk, dev-dax: Update descriptions Robert Elliott
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=20170104065453.15106-1-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.