From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2] io: fix really slow dio_sparse on certain systems
Date: Mon, 26 Jan 2026 16:47:02 +0100 [thread overview]
Message-ID: <aXeMdm4QgIJQ43dk@yuki.lan> (raw)
In-Reply-To: <DFYM56BKO470.2QDB95UE8IOVU@suse.com>
Hi!
> This is definetly a possible solution. I sent this patch by waiting for
> some feebacks in order to have other opinions. What puzzles me is that
> it's only happening in POWER10 on a random node during kernel tests.
> Other architectures seem to work fine.
>
> kernel 6.6+ seems to be the affected one.
>
> >
> > However the test should finish as fast as the writer finishes writing
> > the file. So slow readers shouldn't matter unless there is some serious
> > contention on the disk I/O. That's probably the reason you are aligning
> > the writer as well.
>
> Exactly, I would expect that.
>
> >
> > What is the difference in runtime between test before and after this
> > patch on the slow hardware?
>
> DS009 from 4 hours to 30 seconds. I also profiled the list of syscalls
> with perf, obtaining a 63+ % of io_read() time consumption. Still, this
> patch moves the execution from ~10 secs to ~3 secs on my laptop. There's
> a big difference between 4h and 10 secs runtime, no matter the hard disk
> which is running below.
Honestly that does sound like a kernel bug. You shouldn't get several
orders of magnitude slower just because your buffer is 4 times smaller.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-01-26 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 8:41 [LTP] [PATCH v2] io: fix really slow dio_sparse on certain systems Andrea Cervesato
2026-01-26 11:16 ` Petr Vorel
2026-01-26 11:42 ` Cyril Hrubis
2026-01-26 11:44 ` Cyril Hrubis
2026-01-26 15:07 ` Andrea Cervesato via ltp
2026-01-26 15:47 ` Cyril Hrubis [this message]
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=aXeMdm4QgIJQ43dk@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.