HOWTO: note that clat/slat can be in micro or mili seconds
authorJens Axboe <jens.axboe@oracle.com>
Tue, 19 Jun 2007 07:53:31 +0000 (09:53 +0200)
committerJens Axboe <jens.axboe@oracle.com>
Tue, 19 Jun 2007 07:53:31 +0000 (09:53 +0200)
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
HOWTO

diff --git a/HOWTO b/HOWTO
index 0c243076ef65be503d7fc17d63ba4f7737182ec9..4d103c846a4d7945f5cdb19d18a27c8b4139760c 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -723,7 +723,10 @@ runt=              The runtime of that thread
        slat=   Submission latency (avg being the average, stdev being the
                standard deviation). This is the time it took to submit
                the io. For sync io, the slat is really the completion
-               latency, since queue/complete is one operation there.
+               latency, since queue/complete is one operation there. This
+               value can be in miliseconds or microseconds, fio will choose
+               the most appropriate base and print that. In the example
+               above, miliseconds is the best scale.
        clat=   Completion latency. Same names as slat, this denotes the
                time from submission to completion of the io pieces. For
                sync io, clat will usually be equal (or very close) to 0,