From: Niklas Cassel <cassel@kernel.org>
To: axboe@kernel.dk, vincentfu@gmail.com
Cc: fio@vger.kernel.org, dlemoal@kernel.org,
Niklas Cassel <cassel@kernel.org>
Subject: [PATCH 1/2] examples: cmdprio_bssplit: s,IO,I/O,
Date: Fri, 26 Jan 2024 19:13:52 +0100 [thread overview]
Message-ID: <20240126181353.4151771-1-cassel@kernel.org> (raw)
Replace IO with I/O.
Signed-off-by: Niklas Cassel <cassel@kernel.org>
---
examples/cmdprio-bssplit.fio | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/examples/cmdprio-bssplit.fio b/examples/cmdprio-bssplit.fio
index f3b2fac0..05f0d0b2 100644
--- a/examples/cmdprio-bssplit.fio
+++ b/examples/cmdprio-bssplit.fio
@@ -12,9 +12,9 @@ iodepth=16
; use the same prio class and prio level defined by the cmdprio_class
; and cmdprio options.
[cmdprio]
-; 40% of read IOs are 64kB and 60% are 1MB. 100% of writes are 1MB.
+; 40% of read I/Os are 64kB and 60% are 1MB. 100% of writes are 1MB.
; 100% of the 64kB reads are executed with prio class 1 and prio level 0.
-; All other IOs are executed without a priority set.
+; All other I/Os are executed without a priority set.
bssplit=64k/40:1024k/60,1024k/100
cmdprio_bssplit=64k/100:1024k/0,1024k/0
cmdprio_class=1
@@ -23,20 +23,20 @@ cmdprio=0
; Advanced cmdprio_bssplit format. Each non-zero percentage entry can
; use a different prio class and prio level (appended to each entry).
[cmdprio-adv]
-; 40% of read IOs are 64kB and 60% are 1MB. 100% of writes are 1MB.
+; 40% of read I/Os are 64kB and 60% are 1MB. 100% of writes are 1MB.
; 25% of the 64kB reads are executed with prio class 1 and prio level 1,
; 75% of the 64kB reads are executed with prio class 3 and prio level 2.
-; All other IOs are executed without a priority set.
+; All other I/Os are executed without a priority set.
stonewall
bssplit=64k/40:1024k/60,1024k/100
cmdprio_bssplit=64k/25/1/1:64k/75/3/2:1024k/0,1024k/0
; Identical to the previous example, but with a default priority defined.
[cmdprio-adv-def]
-; 40% of read IOs are 64kB and 60% are 1MB. 100% of writes are 1MB.
+; 40% of read I/Os are 64kB and 60% are 1MB. 100% of writes are 1MB.
; 25% of the 64kB reads are executed with prio class 1 and prio level 1,
; 75% of the 64kB reads are executed with prio class 3 and prio level 2.
-; All other IOs are executed with prio class 2 and prio level 7.
+; All other I/Os are executed with prio class 2 and prio level 7.
stonewall
prioclass=2
prio=7
--
2.43.0
next reply other threads:[~2024-01-26 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 18:13 Niklas Cassel [this message]
2024-01-26 18:13 ` [PATCH 2/2] examples: cmdprio_bssplit: add CDL example Niklas Cassel
2024-01-27 16:23 ` [PATCH 1/2] examples: cmdprio_bssplit: s,IO,I/O, Vincent Fu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240126181353.4151771-1-cassel@kernel.org \
--to=cassel@kernel.org \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=fio@vger.kernel.org \
--cc=vincentfu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).