Skip to contentSkip to conversation

doc: clarify the usage of rw_sequencer

PATCH Applied Ankit Kumar 2 participants 3 messages Jan 11, 2023 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): CGME20230111064841epcas5p3b26ec4b04ab5ddbfc5ce4caea0dc4687@epcas5p3.samsung.com

#1 lore raw

v2 cover Update doc for option rw_sequencer

Changes since v1:
- Changed the wording for rw_sequencer=sequential as per Vincent's feedback.
- Added few examples explaining about rw_sequencer.

Ankit Kumar (1):
doc: clarify the usage of rw_sequencer

 HOWTO.rst | 35 ++++++++++++++++++++++++++++-------
 fio.1     | 47 +++++++++++++++++++++++++++++++++++++++++------
 2 files changed, 69 insertions(+), 13 deletions(-)
Signature · 1 line
2.17.1
#2 lore raw

PATCH v2 1/1 doc: clarify the usage of rw_sequencer

Update man page clarifying the usage of rw_sequencer=sequential Added few examples explaining the offset generation for rw_sequencer.

---
 HOWTO.rst | 35 ++++++++++++++++++++++++++++-------
 fio.1     | 47 +++++++++++++++++++++++++++++++++++++++++------
 2 files changed, 69 insertions(+), 13 deletions(-)
HOWTO.rst +28 -7
index 0a48a453..17caaf5d 100644
@@ -1176,13 +1176,34 @@ I/O type
 			Generate the same offset.
 
 	``sequential`` is only useful for random I/O, where fio would normally
-	generate a new random offset for every I/O. If you append e.g. 8 to randread,
-	you would get a new random offset for every 8 I/Os. The result would be a
-	seek for only every 8 I/Os, instead of for every I/O. Use ``rw=randread:8``
-	to specify that. As sequential I/O is already sequential, setting
-	``sequential`` for that would not result in any differences.  ``identical``
-	behaves in a similar fashion, except it sends the same offset 8 number of
-	times before generating a new offset.
+	generate a new random offset for every I/O. If you append e.g. 8 to
+	randread, i.e. ``rw=randread:8`` you would get a new random offset for
+	every 8 I/Os. The result would be a sequence of 8 sequential offsets
+	with a random starting point. However this behavior may change if a
+	sequential I/O reaches end of the file. As sequential I/O is already
+	sequential, setting ``sequential`` for that would not result in any
+	difference. ``identical`` behaves in a similar fashion, except it sends
+	the same offset 8 number of times before generating a new offset.
+
+	Example #1::
+
+		rw=randread:8
+		rw_sequencer=sequential
+		bs=4k
+
+	The generated sequence of offsets will look like this:
+	4k, 8k, 12k, 16k, 20k, 24k, 28k, 32k, 92k, 96k, 100k, 104k, 108k,
+	112k, 116k, 120k, 48k, 52k ...
+
+	Example #2::
+
+		rw=randread:8
+		rw_sequencer=identical
+		bs=4k
+
+	The generated sequence of offsets will look like this:
+	4k, 4k, 4k, 4k, 4k, 4k, 4k, 4k, 92k, 92k, 92k, 92k, 92k, 92k, 92k, 92k,
+	48k, 48k, 48k ...
 
 .. option:: unified_rw_reporting=str
 
fio.1 +41 -6

53 lines not on this page · raw message

Signature · 1 line
2.17.1
Applied
#3 lore raw

Re: [PATCH v2 0/1] Update doc for option rw_sequencer

In reply to Ankit Kumar
Quoted 7 lines · Ankit Kumar

Changes since v1:
- Changed the wording for rw_sequencer=sequential as per Vincent's feedback.
- Added few examples explaining about rw_sequencer.

Quoted 7 lines

Ankit Kumar (1):
doc: clarify the usage of rw_sequencer

  HOWTO.rst | 35 ++++++++++++++++++++++++++++-------
  fio.1     | 47 +++++++++++++++++++++++++++++++++++++++++------
  2 files changed, 69 insertions(+), 13 deletions(-)

Applied. Thanks.