From: Sitsofe Wheeler Date: Wed, 21 Jun 2017 06:29:54 +0000 (+0100) Subject: HOWTO: reword iodepth and submit distribution text X-Git-Tag: fio-2.99~34 X-Git-Url: https://git.kernel.dk/?a=commitdiff_plain;h=a2140525a72d0b6bd4aea0d72b606ce3d572c4b3;p=fio.git HOWTO: reword iodepth and submit distribution text Reword the explanation text so phrasing of iodepth and submit distributions is more similar. Also draw attention to the fact the value represents the end-point in iodepth distributions and the start-point in submit distributions. Signed-off-by: Sitsofe Wheeler --- diff --git a/HOWTO b/HOWTO index 0992cfe3..b1904d44 100644 --- a/HOWTO +++ b/HOWTO @@ -3104,16 +3104,20 @@ denote: context and fault counters are summed. **IO depths** - The distribution of I/O depths over the job life time. The numbers are - divided into powers of 2, so for example the 16= entries includes depths - up to that value but higher than the previous entry. In other words, it - covers the range from 16 to 31. + The distribution of I/O depths over the job lifetime. The numbers are + divided into powers of 2 and each entry covers depths from that value + up to those that are lower than the next entry -- e.g., 16= covers + depths from 16 to 31. Note that the range covered by a depth + distribution entry can be different to the range covered by the + equivalent submit/complete distribution entry. **IO submit** How many pieces of I/O were submitting in a single submit call. Each entry denotes that amount and below, until the previous entry -- e.g., - 8=100% mean that we submitted anywhere in between 5-8 I/Os per submit - call. + 16=100% means that we submitted anywhere between 9 to 16 I/Os per submit + call. Note that the range covered by a submit distribution entry can + be different to the range covered by the equivalent depth distribution + entry. **IO complete** Like the above submit number, but for completions instead.