The following changes since commit e07f72d341ded8cfa539abf377322ab1b7473960:
RDMA I/O engine: Fix compiler warnings (2011-08-07 21:50:52 +0200)
are available in the git repository at:
git://git.kernel.dk/fio.git master
Jens Axboe (3):
Merge branch 'master' of ssh://router/data/git/fio
Update softrandommap in HOWTO
man page typo
Zhu Yanhai (1):
Fix a typo in fio.1
HOWTO | 8 ++++----
fio.1 | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
---
Diff of recent changes:
diff --git a/HOWTO b/HOWTO
index 88bd5e6..b47d733 100644
--- a/HOWTO
+++ b/HOWTO
@@ -678,10 +678,10 @@ norandommap Normally fio will cover every block of the file when doing
blocksizes (via bsrange=) are used, since fio only tracks
complete rewrites of blocks.
-softrandommap See norandommap. If fio runs with the random block map enabled
- and it fails to allocate the map, if this option is set it
- will continue without a random block map. As coverage will
- not be as complete as with random maps, this option is
+softrandommap=bool See norandommap. If fio runs with the random block map
+ enabled and it fails to allocate the map, if this option is
+ set it will continue without a random block map. As coverage
+ will not be as complete as with random maps, this option is
disabled by default.
nice=int Run the job with the given nice value. See man nice(2).
diff --git a/fio.1 b/fio.1
index 21ccda5..4fcd511 100644
--- a/fio.1
+++ b/fio.1
@@ -512,7 +512,7 @@ Normally \fBfio\fR will cover every block of the file when doing random I/O. If
this parameter is given, a new offset will be chosen without looking at past
I/O history. This parameter is mutually exclusive with \fBverify\fR.
.TP
-.B softrandommap
+.BI softrandommap \fR=\fPbool
See \fBnorandommap\fR. If fio runs with the random block map enabled and it
fails to allocate the map, if this option is set it will continue without a
random block map. As coverage will not be as complete as with random maps, this
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
