Skip to contentSkip to conversation

documentation update for size

PATCH Applied Ankit Kumar 2 participants 3 messages Dec 1, 2022 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): CGME20221201052003epcas5p27b512af6c584d1e7e4ba95efb3668371@epcas5p2.samsung.com

#1 lore raw

v2 cover documentation update for size

There are cases with fio option size that the number of bytes of data transferred is less than what is specified. This can happen if there are gaps or holes while doing I/O's or if we are running a mix of sequential and random workload. Update the documentation for that.

Changes since v1:
- Drop the code changes and only update the doc as suggested by Vincent.

Ankit Kumar (1):
doc: update about size

 HOWTO.rst | 7 +++++--
 fio.1     | 7 +++++--
 2 files changed, 10 insertions(+), 4 deletions(-)
Signature · 1 line
2.17.1
#2 lore raw

PATCH v2 1/1 doc: update about size

In few cases with fio option size the number of bytes of data transferred is actually less than what we specified. This can happen if there are gaps or holes while doing I/O's or if we are running a mix of sequential and random workload.
Update the documentation for that.

---
 HOWTO.rst | 7 +++++--
 fio.1     | 7 +++++--
 2 files changed, 10 insertions(+), 4 deletions(-)
HOWTO.rst +5 -2
index 2ea84558..0aaf033a 100644
@@ -1875,8 +1875,11 @@ I/O size
 .. option:: size=int
 
 	The total size of file I/O for each thread of this job. Fio will run until
-	this many bytes has been transferred, unless runtime is limited by other options
-	(such as :option:`runtime`, for instance, or increased/decreased by :option:`io_size`).
+	this many bytes has been transferred, unless runtime is altered by other means
+	such as (1) :option:`runtime`, (2) :option:`io_size` (3) :option:`number_ios`,
+	(4) gaps/holes while doing I/O's such as ``rw=read:16K``, or (5) sequential
+	I/O reaching end of the file which is possible when :option:`percentage_random`
+	is less than 100.
 	Fio will divide this size between the available files determined by options
 	such as :option:`nrfiles`, :option:`filename`, unless :option:`filesize` is
 	specified by the job. If the result of division happens to be 0, the size is
fio.1 +5 -2
index 746c4472..62af0bd2 100644
@@ -1676,8 +1676,11 @@ simulate a smaller amount of memory. The amount specified is per worker.
 .TP
 .BI size \fR=\fPint[%|z]
 The total size of file I/O for each thread of this job. Fio will run until
-this many bytes has been transferred, unless runtime is limited by other options
-(such as \fBruntime\fR, for instance, or increased/decreased by \fBio_size\fR).
+this many bytes has been transferred, unless runtime is altered by other means
+such as (1) \fBruntime\fR, (2) \fBio_size\fR, (3) \fBnumber_ios\fR, (4)
+gaps/holes while doing I/O's such as `rw=read:16K', or (5) sequential I/O
+reaching end of the file which is possible when \fBpercentage_random\fR is
+less than 100.
 Fio will divide this size between the available files determined by options
 such as \fBnrfiles\fR, \fBfilename\fR, unless \fBfilesize\fR is
 specified by the job. If the result of division happens to be 0, the size is
Signature · 1 line
2.17.1
Applied
#3 lore raw
In reply to Ankit Kumar
Quoted 11 lines · Ankit Kumar

There are cases with fio option size that the number of bytes of data transferred is less than what is specified. This can happen if there are gaps or holes while doing I/O's or if we are running a mix of sequential and random workload. Update the documentation for that.

Changes since v1:
- Drop the code changes and only update the doc as suggested by Vincent.

Quoted 7 lines

Ankit Kumar (1):
doc: update about size

  HOWTO.rst | 7 +++++--
  fio.1     | 7 +++++--
  2 files changed, 10 insertions(+), 4 deletions(-)

Applied. Thanks.