From: Jeff Layton <jlayton@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
linux-block@vger.kernel.org, Jeff Layton <jlayton@kernel.org>
Subject: [PATCH] blkcg: update iocost_coef_gen.py to use io_uring
Date: Wed, 24 Jun 2026 10:50:34 -0400 [thread overview]
Message-ID: <20260624-iocost-v1-1-2d53f3c026a2@kernel.org> (raw)
Recently I found myself having to benchmark some rather fast disks for
iocost, but the old iocost_coef_gen.py script couldn't generate enough
throughput to saturate it. Make it use io_uring instead.
Cc: Tejun Heo <tj@kernel.org>
Cc: linux-block@vger.kernel.org
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
tools/cgroup/iocost_coef_gen.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/cgroup/iocost_coef_gen.py b/tools/cgroup/iocost_coef_gen.py
index df17a2ae80e5..41f93f4536cc 100644
--- a/tools/cgroup/iocost_coef_gen.py
+++ b/tools/cgroup/iocost_coef_gen.py
@@ -91,7 +91,7 @@ def run_fio(testfile, duration, iotype, iodepth, blocksize, jobs):
eta = 'never' if args.quiet else 'always'
outfile = tempfile.NamedTemporaryFile()
- cmd = (f'fio --direct=1 --ioengine=libaio --name=coef '
+ cmd = (f'fio --direct=1 --ioengine=io_uring --name=coef '
f'--filename={testfile} --runtime={round(duration)} '
f'--readwrite={iotype} --iodepth={iodepth} --blocksize={blocksize} '
f'--eta={eta} --output-format json --output={outfile.name} '
---
base-commit: 840ef6c78e6a2f694b578ecb9063241c992aaa9e
change-id: 20260624-iocost-a196820cc049
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2026-06-24 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 14:50 Jeff Layton [this message]
2026-06-24 16:48 ` Tejun Heo
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=20260624-iocost-v1-1-2d53f3c026a2@kernel.org \
--to=jlayton@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®