document the --scsi option

diff --git a/doc/dbench.1 b/doc/dbench.1
index 39e7b7a3d6492403d115c14b39d241a1bc9cbab7..f5f66f988dbc37a8d875613762980fc4bd585966 100644 (file)
--- a/doc/dbench.1
+++ b/doc/dbench.1
@@ -1,116 +1,129 @@
 .\"     Title: dbench
 .\"    Author: 
 .\"     Title: dbench
 .\"    Author: 

-.\" Generator: DocBook XSL Stylesheets v1.71.0 <http://docbook.sf.net/>
-.\"      Date: 08/19/2008
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 10/17/2008

 .\"    Manual: 
 .\"    Source: 
 .\"
 .\"    Manual: 
 .\"    Source: 
 .\"

-.TH "DBENCH" "1" "08/19/2008" "" ""
+.TH "DBENCH" "1" "10/17/2008" "" ""

 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
 .ad l
 .SH "NAME"
 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
 .ad l
 .SH "NAME"

-dbench \- a benchmark tool
+dbench - a benchmark tool

 .SH "SYNOPSIS"
 .HP 29
 \fBdbench [OPTIONS] <num\-procs>\fR
 .HP 7
 .SH "SYNOPSIS"
 .HP 29
 \fBdbench [OPTIONS] <num\-procs>\fR
 .HP 7

-\fBdbench\fR [\-B\ \-\-backend=<dbench\ backend>] [\-c\ \-\-loadfile=<filename>] [\-D\ \-\-directory=<string>] [\-F\ \-\-fsync] [\-R\ \-\-target\-rate=<double>] [\-s\ \-\-sync] [\-S\ \-\-sync\-dir] [\-t\ \-\-timelimit=<integer>] [\-T\ \-\-tcp\-options=<string>] [\-\-run\-once] [\-\-fake\-io] [\-\-server=<hostname>] [\-\-export=<string>] [\-\-protocol=<string>] [\-\-clients\-per\-process=<integer>] [\-\-stat\-check] [\-\-skip\-cleanup] [\-\-per\-client\-results] [\-?\ \-\-help] [\-\-usage]
+\fBdbench\fR [\-B\ \-\-backend=<dbench\ backend>] [\-c\ \-\-loadfile=<filename>] [\-D\ \-\-directory=<string>] [\-F\ \-\-fsync] [\-R\ \-\-target\-rate=<double>] [\-s\ \-\-sync] [\-S\ \-\-sync\-dir] [\-t\ \-\-timelimit=<integer>] [\-T\ \-\-tcp\-options=<string>] [\-\-run\-once] [\-\-fake\-io] [\-\-scsi=<scsi\-device>] [\-\-server=<hostname>] [\-\-export=<string>] [\-\-protocol=<string>] [\-\-clients\-per\-process=<integer>] [\-\-trunc\-io=<integer>] [\-\-stat\-check] [\-\-skip\-cleanup] [\-\-per\-client\-results] [\-?\ \-\-help] [\-\-usage]

 .SH "DESCRIPTION"
 .PP
 .SH "DESCRIPTION"
 .PP

-dbench is a utility to benchmark a system based on client workload profiles.
+dbench is a utility to benchmark a system based on client workload profiles\.

 .SH "STANDARD OPTIONS"
 .SS "\-B \-\-backend=<dbench backend>"
 .PP
 .SH "STANDARD OPTIONS"
 .SS "\-B \-\-backend=<dbench backend>"
 .PP

-The backend type specifies which kind of commandset and what kind of tests that dbench will perform. The backend type specifies which kind of loadfile that can be used.
+The backend type specifies which kind of commandset and what kind of tests that dbench will perform\. The backend type specifies which kind of loadfile that can be used\.

 .PP
 .PP

-There are currently three types of backends : "fileio", "sockio" and "nfs". The default is "fileio" which uses a CIFS style loadfile.
+There are currently four types of backends : "fileio", "sockio", "nfs" and "scsi"\. The default is "fileio" which uses a CIFS style loadfile\.

 .SS "\-c \-\-loadfile=<filename>"
 .PP
 .SS "\-c \-\-loadfile=<filename>"
 .PP

-This specifies the name of the loadfile to use. The loadfile describes the sequence and timing of operations that dbench will issue.
+This specifies the name of the loadfile to use\. The loadfile describes the sequence and timing of operations that dbench will issue\.

 .SS "\-D \-\-directory=<string>"
 .PP
 .SS "\-D \-\-directory=<string>"
 .PP

-This controls which directory that dbench will use as the root for when running the loadfile. This defaults to "." which refers to the current directory for the "fileio" and "sockio" backends and the root of the export for the "nfs" backend.
+This controls which directory that dbench will use as the root for when running the loadfile\. This defaults to "\." which refers to the current directory for the "fileio" and "sockio" backends and the root of the export for the "nfs" backend\.

 .SS "\-R \-\-target\-rate=<double>"
 .PP
 .SS "\-R \-\-target\-rate=<double>"
 .PP

-By default dbench will try to replay the loadfile and keep the same rate as the original application the loadfile was captured from. Using this option it is possible to run the load file faster/slower than in the original capture.
+By default dbench will try to replay the loadfile and keep the same rate as the original application the loadfile was captured from\. Using this option it is possible to run the load file faster/slower than in the original capture\.

 .PP
 .PP

-The argument is specified in MByte/second. dbench tries to match this target rate by dynamically increasing/decreasing the delays beteen the inidvidual opertaions in the loadfile. These calculations only take the READ and WRITE operations of the loadfile into account so this may not work reliable for loadfiles with very few READ/WRITE operations.
+The argument is specified in MByte/second\. dbench tries to match this target rate by dynamically increasing/decreasing the delays beteen the inidvidual opertaions in the loadfile\. These calculations only take the READ and WRITE operations of the loadfile into account so this may not work reliable for loadfiles with very few READ/WRITE operations\.

 .PP
 .PP

-By setting this limit to something very large, such as 999999.99 you can effectively tell dbench to "run this loadfile as fast as possible".
+By setting this limit to something very large, such as 999999\.99 you can effectively tell dbench to "run this loadfile as fast as possible"\.

 .SS "\-t \-\-timelimit=<integer>"
 .PP
 .SS "\-t \-\-timelimit=<integer>"
 .PP

-How long to run the test for.
+How long to run the test for\.

 .SS "\-\-run\-once"
 .PP
 .SS "\-\-run\-once"
 .PP

-Only run the loadfile once and stop when the end of the loadfile is reached.
+Only run the loadfile once and stop when the end of the loadfile is reached\.

 .PP
 .PP

-The default for dbench is to wrap the loadfile when the end is reached and continue running the loadfile over and over until the timelimit is reached.
+The default for dbench is to wrap the loadfile when the end is reached and continue running the loadfile over and over until the timelimit is reached\.

 .SS "\-\-clients\-per\-process=<integer>"
 .PP
 .SS "\-\-clients\-per\-process=<integer>"
 .PP

-By default dbench will fork one child process for each client emulated. Using this option dbench will run multiple emulated clients inside each process.
+By default dbench will fork one child process for each client emulated\. Using this option dbench will run multiple emulated clients inside each process\.

 .PP
 .PP

-This is useful for testing how performance differs between the case of n processes with one thread of I/O each and one process with n threads of I/O.
+This is useful for testing how performance differs between the case of n processes with one thread of I/O each and one process with n threads of I/O\.

 .SS "\-\-skip\-cleanup"
 .PP
 .SS "\-\-skip\-cleanup"
 .PP

-Do not cleanup and delete all temporary files in the clients work directory when the test ends.
+Do not cleanup and delete all temporary files in the clients work directory when the test ends\.

 .SS "\-\-per\-client\-results"
 .PP
 .SS "\-\-per\-client\-results"
 .PP

-When the test is finished print a latency report for each inidvidual client in addition to the aggregated report over all clients.
+When the test is finished print a latency report for each inidvidual client in addition to the aggregated report over all clients\.

 .SH "FILEIO OPTIONS"
 .SS "\-F \-\-fsync"
 .PP
 .SH "FILEIO OPTIONS"
 .SS "\-F \-\-fsync"
 .PP

-This option only apply to the "fileio" backend.
+This option only apply to the "fileio" backend\.

 .PP
 .PP

-This will make dbench perform a fsync() to the file after each write operation.
+This will make dbench perform a fsync() to the file after each write operation\.

 .SS "\-s \-\-sync\-open"
 .PP
 .SS "\-s \-\-sync\-open"
 .PP

-This option only apply to the "fileio" backend.
+This option only apply to the "fileio" backend\.

 .PP
 .PP

-This makes dbench override the loadfile and use O_SYNC for all file open operations.
+This makes dbench override the loadfile and use O_SYNC for all file open operations\.

 .SS "\-S \-\-sync\-dir"
 .PP
 .SS "\-S \-\-sync\-dir"
 .PP

-This option only apply to the "fileio" backend.
+This option only apply to the "fileio" backend\.

 .PP
 .PP

-Call fsync() on the directory after each "unlink", "rmdir" or "rename" operation. This emulates how the linux kernel nfs daemon syncs directories after performing directory modifying operations.
+Call fsync() on the directory after each "unlink", "rmdir" or "rename" operation\. This emulates how the linux kernel nfs daemon syncs directories after performing directory modifying operations\.

 .SS "\-\-fake\-io"
 .PP
 .SS "\-\-fake\-io"
 .PP

-This option only apply to the "fileio" backend.
+This option only apply to the "fileio" backend\.

 .PP
 .PP

-Do not do any file read/write operations at all.
+Do not do any file read/write operations at all\.

 .SS "\-\-stat\-check"
 .PP
 .SS "\-\-stat\-check"
 .PP

-This option only apply to the "fileio" backend.
+This option only apply to the "fileio" backend\.

 .PP
 .PP

-After each create/mkdir/rmdir/rename operation, immediately try to stat() the object affected and verify that the return code from stat() is correct. I.e. Verify that immediately after we have created an object that stat() will succeed and that immediately after we have deleted an object that stat() will fail.
+After each create/mkdir/rmdir/rename operation, immediately try to stat() the object affected and verify that the return code from stat() is correct\. I\.e\. Verify that immediately after we have created an object that stat() will succeed and that immediately after we have deleted an object that stat() will fail\.

 .SH "SOCKIO OPTIONS"
 .SS "\-T \-\-tcp\-options=<string>"
 .PP
 .SH "SOCKIO OPTIONS"
 .SS "\-T \-\-tcp\-options=<string>"
 .PP

-This option only apply to the "sockio" backend.
+This option only apply to the "sockio" backend\.

 .SH "NFS OPTIONS"
 .SS "\-\-server=<hostname>"
 .PP
 .SH "NFS OPTIONS"
 .SS "\-\-server=<hostname>"
 .PP

-This option only apply to the "nfs" backend.
+This option only apply to the "nfs" backend\.

 .PP
 .PP

-This option is mandatory when the "nfs" backend is used.
+This option is mandatory when the "nfs" backend is used\.

 .PP
 .PP

-This specifies the host\-name or ip\-address of the server to test.
+This specifies the host\-name or ip\-address of the server to test\.

 .SS "\-\-export=<string>"
 .PP
 .SS "\-\-export=<string>"
 .PP

-This option only apply to the "nfs" backend.
+This option only apply to the "nfs" backend\.

 .PP
 .PP

-This option is mandatory when the "nfs" backend is used.
+This option is mandatory when the "nfs" backend is used\.

 .PP
 .PP

-This specifies the nfs\-export on the server to do i/o to.
+This specifies the nfs\-export on the server to do i/o to\.

 .SS "\-\-protocol=<string>"
 .PP
 .SS "\-\-protocol=<string>"
 .PP

-This option only apply to the "nfs" backend.
+This option only apply to the "nfs" backend\.

 .PP
 .PP

-This specifies whether "tcp" or "udp" is to be used. Default is "tcp".
+This specifies whether "tcp" or "udp" is to be used\. Default is "tcp"\.
+.SS "\-\-trunc\-io=<integer>"
+.PP
+This option only apply to the "nfs" backend\.
+.PP
+Some NFS server may have limitations on how large READ/WRITE I/Os they accept preventing some loadfiles from running\. Using this option will override the length specified in the loadfile and make dbench never issuing any READ/WRITE operations larger than this\.
+.SH "SCSI OPTIONS"
+.SS "\-\-scsi=<scsi\-device>"
+.PP
+This option only apply to the "scsi" backend\.
+.PP
+This option is mandatory when the "scsi" backend is used\.
+.PP
+This specifies the device node of the scsi\-device we want to run the loadfile on\. Example: \-\-scsi=/dev/sda

 .SH "COPYRIGHT/LICENSE"
 .sp
 .SH "COPYRIGHT/LICENSE"
 .sp

-.RS 3n
+.RS 4

 .nf
 Copyright (C) Andrew Tridgell 2008
 Copyright (C) Ronnie Sahlberg 2008
 .nf
 Copyright (C) Andrew Tridgell 2008
 Copyright (C) Ronnie Sahlberg 2008


@@ -118,14 +131,14 @@ Copyright (C) Ronnie Sahlberg 2008
 This program is free software; you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by
 the Free Software Foundation; either version 3 of the License, or (at
 This program is free software; you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by
 the Free Software Foundation; either version 3 of the License, or (at

-your option) any later version.
+your option) any later version\.

 
 This program is distributed in the hope that it will be useful, but
 WITHOUT ANY WARRANTY; without even the implied warranty of
 
 This program is distributed in the hope that it will be useful, but
 WITHOUT ANY WARRANTY; without even the implied warranty of

-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
-General Public License for more details.
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\.  See the GNU
+General Public License for more details\.

 
 You should have received a copy of the GNU General Public License
 
 You should have received a copy of the GNU General Public License

-along with this program; if not, see http://www.gnu.org/licenses/.
+along with this program; if not, see http://www\.gnu\.org/licenses/\.

 .fi
 .RE
 .fi
 .RE

diff --git a/doc/dbench.1.html b/doc/dbench.1.html
index 8a6c5b610023131610e1ab81ceede8d0edd0cfce..b4c488abcbd258bf0dbf4c77a52543cd2eb17edc 100644 (file)
--- a/doc/dbench.1.html
+++ b/doc/dbench.1.html
@@ -1,21 +1,21 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>dbench</title><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="dbench.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>dbench &#8212; a benchmark tool</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">dbench [OPTIONS] &lt;num-procs&gt;</code> </p></div><div class="cmdsynopsis"><p><code class="command">dbench</code>  [-B --backend=&lt;dbench backend&gt;] [-c --loadfile=&lt;filename&gt;] [-D --directory=&lt;string&gt;] [-F --fsync] [-R --target-rate=&lt;double&gt;] [-s --sync] [-S --sync-dir] [-t --timelimit=&lt;integer&gt;] [-T --tcp-options=&lt;string&gt;] [--run-once] [--fake-io] [--server=&lt;hostname&gt;] [--export=&lt;string&gt;] [--protocol=&lt;string&gt;] [--clients-per-process=&lt;integer&gt;] [--stat-check] [--skip-cleanup] [--per-client-results] [-? --help] [--usage]</p></div></div><div class="refsect1" lang="en"><a name="id2481142"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>dbench</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="dbench.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>dbench &#8212; a benchmark tool</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">dbench [OPTIONS] &lt;num-procs&gt;</code> </p></div><div class="cmdsynopsis"><p><code class="command">dbench</code>  [-B --backend=&lt;dbench backend&gt;] [-c --loadfile=&lt;filename&gt;] [-D --directory=&lt;string&gt;] [-F --fsync] [-R --target-rate=&lt;double&gt;] [-s --sync] [-S --sync-dir] [-t --timelimit=&lt;integer&gt;] [-T --tcp-options=&lt;string&gt;] [--run-once] [--fake-io] [--scsi=&lt;scsi-device&gt;] [--server=&lt;hostname&gt;] [--export=&lt;string&gt;] [--protocol=&lt;string&gt;] [--clients-per-process=&lt;integer&gt;] [--trunc-io=&lt;integer&gt;] [--stat-check] [--skip-cleanup] [--per-client-results] [-? --help] [--usage]</p></div></div><div class="refsect1" lang="en"><a name="id2479642"></a><h2>DESCRIPTION</h2><p>

       dbench is a utility to benchmark a system based on client workload
       profiles.
       dbench is a utility to benchmark a system based on client workload
       profiles.

-    </p></div><div class="refsect1" lang="en"><a name="id2481152"></a><h2>STANDARD OPTIONS</h2><div class="refsect2" lang="en"><a name="id2481158"></a><h3>-B --backend=&lt;dbench backend&gt;</h3><p>
+    </p></div><div class="refsect1" lang="en"><a name="id2479653"></a><h2>STANDARD OPTIONS</h2><div class="refsect2" lang="en"><a name="id2479658"></a><h3>-B --backend=&lt;dbench backend&gt;</h3><p>

       The backend type specifies which kind of commandset and what kind of
       tests that dbench will perform. The backend type specifies which
       kind of loadfile that can be used.
       </p><p>
       The backend type specifies which kind of commandset and what kind of
       tests that dbench will perform. The backend type specifies which
       kind of loadfile that can be used.
       </p><p>

-      There are currently three types of backends : "fileio", "sockio" and "nfs". The default is "fileio" which uses a CIFS style loadfile.
-      </p></div><div class="refsect2" lang="en"><a name="id2481176"></a><h3>-c --loadfile=&lt;filename&gt;</h3><p>
+      There are currently four types of backends : "fileio", "sockio", "nfs" and "scsi". The default is "fileio" which uses a CIFS style loadfile.
+      </p></div><div class="refsect2" lang="en"><a name="id2479677"></a><h3>-c --loadfile=&lt;filename&gt;</h3><p>

       This specifies the name of the loadfile to use. The loadfile describes
       the sequence and timing of operations that dbench will issue.
       This specifies the name of the loadfile to use. The loadfile describes
       the sequence and timing of operations that dbench will issue.

-      </p></div><div class="refsect2" lang="en"><a name="id2481188"></a><h3>-D --directory=&lt;string&gt;</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2479689"></a><h3>-D --directory=&lt;string&gt;</h3><p>

       This controls which directory that dbench will use as the root for when
       running the loadfile. This defaults to "." which refers to the current
       directory for the "fileio" and "sockio" backends and the root of the
       export for the "nfs" backend.
       This controls which directory that dbench will use as the root for when
       running the loadfile. This defaults to "." which refers to the current
       directory for the "fileio" and "sockio" backends and the root of the
       export for the "nfs" backend.

-      </p></div><div class="refsect2" lang="en"><a name="id2481202"></a><h3>-R --target-rate=&lt;double&gt;</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2479702"></a><h3>-R --target-rate=&lt;double&gt;</h3><p>

       By default dbench will try to replay the loadfile and keep the same
       rate as the original application the loadfile was captured from.
       Using this option it is possible to run the load file faster/slower
       By default dbench will try to replay the loadfile and keep the same
       rate as the original application the loadfile was captured from.
       Using this option it is possible to run the load file faster/slower


@@ -30,16 +30,16 @@
       </p><p>
       By setting this limit to something very large, such as 999999.99 you can
       effectively tell dbench to "run this loadfile as fast as possible".
       </p><p>
       By setting this limit to something very large, such as 999999.99 you can
       effectively tell dbench to "run this loadfile as fast as possible".

-      </p></div><div class="refsect2" lang="en"><a name="id2481232"></a><h3>-t --timelimit=&lt;integer&gt;</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2479732"></a><h3>-t --timelimit=&lt;integer&gt;</h3><p>

       How long to run the test for.
       How long to run the test for.

-      </p></div><div class="refsect2" lang="en"><a name="id2481242"></a><h3>--run-once</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2479741"></a><h3>--run-once</h3><p>

       Only run the loadfile once and stop when the end of the loadfile is
       reached.
       </p><p>
       The default for dbench is to wrap the loadfile when the end is
       reached and continue running the loadfile over and over until the
       timelimit is reached.
       Only run the loadfile once and stop when the end of the loadfile is
       reached.
       </p><p>
       The default for dbench is to wrap the loadfile when the end is
       reached and continue running the loadfile over and over until the
       timelimit is reached.

-      </p></div><div class="refsect2" lang="en"><a name="id2481258"></a><h3>--clients-per-process=&lt;integer&gt;</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2479758"></a><h3>--clients-per-process=&lt;integer&gt;</h3><p>

       By default dbench will fork one child process for each client emulated.
       Using this option dbench will run multiple emulated clients inside
       each process.
       By default dbench will fork one child process for each client emulated.
       Using this option dbench will run multiple emulated clients inside
       each process.


@@ -47,33 +47,33 @@
       This is useful for testing how performance differs between the case
       of n processes with one thread of I/O each and one process with n threads
       of I/O.
       This is useful for testing how performance differs between the case
       of n processes with one thread of I/O each and one process with n threads
       of I/O.

-      </p></div><div class="refsect2" lang="en"><a name="id2481277"></a><h3>--skip-cleanup</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2479777"></a><h3>--skip-cleanup</h3><p>

       Do not cleanup and delete all temporary files in the clients work
       directory when the test ends.
       Do not cleanup and delete all temporary files in the clients work
       directory when the test ends.

-      </p></div><div class="refsect2" lang="en"><a name="id2481288"></a><h3>--per-client-results</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2479788"></a><h3>--per-client-results</h3><p>

       When the test is finished print a latency report for each inidvidual
       client in addition to the aggregated report over all clients.
       When the test is finished print a latency report for each inidvidual
       client in addition to the aggregated report over all clients.

-      </p></div></div><div class="refsect1" lang="en"><a name="id2481300"></a><h2>FILEIO OPTIONS</h2><div class="refsect2" lang="en"><a name="id2481306"></a><h3>-F --fsync</h3><p>
+      </p></div></div><div class="refsect1" lang="en"><a name="id2479800"></a><h2>FILEIO OPTIONS</h2><div class="refsect2" lang="en"><a name="id2479806"></a><h3>-F --fsync</h3><p>

       This option only apply to the "fileio" backend.
       </p><p>
       This will make dbench perform a fsync() to the file after each write
       operation.
       This option only apply to the "fileio" backend.
       </p><p>
       This will make dbench perform a fsync() to the file after each write
       operation.

-      </p></div><div class="refsect2" lang="en"><a name="id2481321"></a><h3>-s --sync-open</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2479821"></a><h3>-s --sync-open</h3><p>

       This option only apply to the "fileio" backend.
       </p><p>
       This makes dbench override the loadfile and use O_SYNC for all 
       file open operations.
       This option only apply to the "fileio" backend.
       </p><p>
       This makes dbench override the loadfile and use O_SYNC for all 
       file open operations.

-      </p></div><div class="refsect2" lang="en"><a name="id2481336"></a><h3>-S --sync-dir</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2479836"></a><h3>-S --sync-dir</h3><p>

       This option only apply to the "fileio" backend.
       </p><p>
       Call fsync() on the directory after each "unlink", "rmdir" or "rename"
       operation. This emulates how the linux kernel nfs daemon syncs
       directories after performing directory modifying operations.
       This option only apply to the "fileio" backend.
       </p><p>
       Call fsync() on the directory after each "unlink", "rmdir" or "rename"
       operation. This emulates how the linux kernel nfs daemon syncs
       directories after performing directory modifying operations.

-      </p></div><div class="refsect2" lang="en"><a name="id2528413"></a><h3>--fake-io</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2528501"></a><h3>--fake-io</h3><p>

       This option only apply to the "fileio" backend.
       </p><p>
       Do not do any file read/write operations at all.
       This option only apply to the "fileio" backend.
       </p><p>
       Do not do any file read/write operations at all.

-      </p></div><div class="refsect2" lang="en"><a name="id2528427"></a><h3>--stat-check</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2528515"></a><h3>--stat-check</h3><p>

       This option only apply to the "fileio" backend.
       </p><p>
       After each create/mkdir/rmdir/rename operation, immediately try to
       This option only apply to the "fileio" backend.
       </p><p>
       After each create/mkdir/rmdir/rename operation, immediately try to


@@ -81,25 +81,38 @@
       is correct. I.e. Verify that immediately after we have created an
       object that stat() will succeed and that immediately after we have
       deleted an object that stat() will fail.
       is correct. I.e. Verify that immediately after we have created an
       object that stat() will succeed and that immediately after we have
       deleted an object that stat() will fail.

-      </p></div></div><div class="refsect1" lang="en"><a name="id2528447"></a><h2>SOCKIO OPTIONS</h2><div class="refsect2" lang="en"><a name="id2528453"></a><h3>-T --tcp-options=&lt;string&gt;</h3><p>
+      </p></div></div><div class="refsect1" lang="en"><a name="id2528535"></a><h2>SOCKIO OPTIONS</h2><div class="refsect2" lang="en"><a name="id2528541"></a><h3>-T --tcp-options=&lt;string&gt;</h3><p>

       This option only apply to the "sockio" backend.
       This option only apply to the "sockio" backend.

-      </p></div></div><div class="refsect1" lang="en"><a name="id2528465"></a><h2>NFS OPTIONS</h2><div class="refsect2" lang="en"><a name="id2528470"></a><h3>--server=&lt;hostname&gt;</h3><p>
+      </p></div></div><div class="refsect1" lang="en"><a name="id2528553"></a><h2>NFS OPTIONS</h2><div class="refsect2" lang="en"><a name="id2528558"></a><h3>--server=&lt;hostname&gt;</h3><p>

       This option only apply to the "nfs" backend.
       </p><p>
       This option is mandatory when the "nfs" backend is used.
       </p><p>
       This specifies the host-name or ip-address of the server to test.
       This option only apply to the "nfs" backend.
       </p><p>
       This option is mandatory when the "nfs" backend is used.
       </p><p>
       This specifies the host-name or ip-address of the server to test.

-      </p></div><div class="refsect2" lang="en"><a name="id2528490"></a><h3>--export=&lt;string&gt;</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2528578"></a><h3>--export=&lt;string&gt;</h3><p>

       This option only apply to the "nfs" backend.
       </p><p>
       This option is mandatory when the "nfs" backend is used.
       </p><p>
       This specifies the nfs-export on the server to do i/o to.
       This option only apply to the "nfs" backend.
       </p><p>
       This option is mandatory when the "nfs" backend is used.
       </p><p>
       This specifies the nfs-export on the server to do i/o to.

-      </p></div><div class="refsect2" lang="en"><a name="id2528509"></a><h3>--protocol=&lt;string&gt;</h3><p>
+      </p></div><div class="refsect2" lang="en"><a name="id2528597"></a><h3>--protocol=&lt;string&gt;</h3><p>

       This option only apply to the "nfs" backend.
       </p><p>
       This specifies whether "tcp" or "udp" is to be used. Default is "tcp".
       This option only apply to the "nfs" backend.
       </p><p>
       This specifies whether "tcp" or "udp" is to be used. Default is "tcp".

-      </p></div></div><div class="refsect1" lang="en"><a name="id2528525"></a><h2>COPYRIGHT/LICENSE</h2><div class="literallayout"><p><br>
+      </p></div><div class="refsect2" lang="en"><a name="id2528612"></a><h3>--trunc-io=&lt;integer&gt;</h3><p>
+      This option only apply to the "nfs" backend.
+      </p><p>
+      Some NFS server may have limitations on how large READ/WRITE I/Os they
+      accept preventing some loadfiles from running. Using this option will
+      override the length specified in the loadfile and make dbench never
+      issuing any READ/WRITE operations larger than this.
+      </p></div></div><div class="refsect1" lang="en"><a name="id2528631"></a><h2>SCSI OPTIONS</h2><div class="refsect2" lang="en"><a name="id2528637"></a><h3>--scsi=&lt;scsi-device&gt;</h3><p>
+      This option only apply to the "scsi" backend.
+      </p><p>
+      This option is mandatory when the "scsi" backend is used.
+      </p><p>
+      This specifies the device node of the scsi-device we want to run the loadfile on. Example: --scsi=/dev/sda
+      </p></div></div><div class="refsect1" lang="en"><a name="id2528659"></a><h2>COPYRIGHT/LICENSE</h2><div class="literallayout"><p><br>

 Copyright (C) Andrew Tridgell 2008<br>
 Copyright (C) Ronnie Sahlberg 2008<br>
 <br>
 Copyright (C) Andrew Tridgell 2008<br>
 Copyright (C) Ronnie Sahlberg 2008<br>
 <br>

diff --git a/doc/dbench.1.xml b/doc/dbench.1.xml
index 7574005ddd1694d139711d7f202fdef26947197f..6b763cc7fde67ac310abbc8cfca6a30a6c7f91c5 100644 (file)
--- a/doc/dbench.1.xml
+++ b/doc/dbench.1.xml
@@ -31,6 +31,7 @@
                <arg choice="opt">-T --tcp-options=&lt;string&gt;</arg>
                <arg choice="opt">--run-once</arg>
                <arg choice="opt">--fake-io</arg>
                <arg choice="opt">-T --tcp-options=&lt;string&gt;</arg>
                <arg choice="opt">--run-once</arg>
                <arg choice="opt">--fake-io</arg>

+               <arg choice="opt">--scsi=&lt;scsi-device&gt;</arg>

                <arg choice="opt">--server=&lt;hostname&gt;</arg>
                <arg choice="opt">--export=&lt;string&gt;</arg>
                <arg choice="opt">--protocol=&lt;string&gt;</arg>
                <arg choice="opt">--server=&lt;hostname&gt;</arg>
                <arg choice="opt">--export=&lt;string&gt;</arg>
                <arg choice="opt">--protocol=&lt;string&gt;</arg>


@@ -66,7 +67,7 @@
       </para>
 
       <para>
       </para>
 
       <para>

-      There are currently three types of backends : "fileio", "sockio" and "nfs". The default is "fileio" which uses a CIFS style loadfile.
+      There are currently four types of backends : "fileio", "sockio", "nfs" and "scsi". The default is "fileio" which uses a CIFS style loadfile.

       </para>
     </refsect2>
 
       </para>
     </refsect2>
 


@@ -282,6 +283,23 @@
     </refsect2>
   </refsect1>
 
     </refsect2>
   </refsect1>
 

+  <refsect1> <title>SCSI OPTIONS</title>
+    <refsect2><title>--scsi=&lt;scsi-device&gt;</title>
+      <para>
+      This option only apply to the "scsi" backend.
+      </para>
+
+      <para>
+      This option is mandatory when the "scsi" backend is used.
+      </para>
+
+      <para>
+      This specifies the device node of the scsi-device we want to run the loadfile on. Example: --scsi=/dev/sda
+      </para>
+    </refsect2>
+  </refsect1>
+
+

   <refsect1><title>COPYRIGHT/LICENSE</title>
 <literallayout>
 Copyright (C) Andrew Tridgell 2008
   <refsect1><title>COPYRIGHT/LICENSE</title>
 <literallayout>
 Copyright (C) Andrew Tridgell 2008