From: Cyril Hrubis <chrubis@suse.cz>
To: Jan Kara <jack@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/2] runtest: ltp-aiodio.part2: Limit the maximal filesize
Date: Fri, 20 Mar 2026 10:51:27 +0100 [thread overview]
Message-ID: <ab0Yn91oOC0TfVOV@yuki.lan> (raw)
In-Reply-To: <xb4a277xjifyrgtwc7xochxc2ysuewk7tioefuje3r6sak3os2@nrgti25k63ul>
Hi!
> > The test was operating with filesize up to ~500MB which, in certain
> > cases, was making the runtime too slow. Some test variants, especially
> > with many processes, were running up to 15 mintues on modern hardware.
> > After a discussion we agreed that we can reduce the maximal file size to
> > one quater without sacrificing test coverage.
> >
> > I've also assumed that there was a typo in ADSP072 since the buffer size
> > was set to be order of magnitude bigger than the file size.
> >
> > CC: Jan Kara <jack@suse.cz>
> > Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
> > ---
> > runtest/ltp-aiodio.part2 | 16 ++++++++--------
> > 1 file changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/runtest/ltp-aiodio.part2 b/runtest/ltp-aiodio.part2
> > index 599c9fd2f..c82f6fd02 100644
> > --- a/runtest/ltp-aiodio.part2
> > +++ b/runtest/ltp-aiodio.part2
> > @@ -25,8 +25,8 @@ ADSP023 aiodio_sparse -o 4 -w 1024k -s 4096k -n 6
> > ADSP024 aiodio_sparse -o 4 -w 2048k -s 8192k -n 6
> > ADSP025 aiodio_sparse -o 4 -w 4096k -s 16384k -n 6
> > ADSP026 aiodio_sparse -o 4 -w 18192k -s 72768k -n 6
> > -ADSP027 aiodio_sparse -o 4 -w 18192k -s 518192k -n 6
> > -ADSP028 aiodio_sparse -o 4 -w 65536k -s 262144k -n 6
> > +ADSP027 aiodio_sparse -o 4 -w 18192k -s 129548k -n 6
> > +ADSP028 aiodio_sparse -o 4 -w 65536k -s 129548k -n 6
>
> I think the write size of 64MB is too large for 128MB file with 4 AIO
> contexts - I think the size will be autotrimmed to 32MB. So you might as
> well just specify -w 32768k.
Right, will fix that.
> Otherwise this looks good to me.
Do I need to send v2 or can I add your Reviewed-by: if I fix the write
size before applying the patches?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-20 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 16:03 [LTP] [PATCH 0/2] Cleanup of aiodio runtest files Cyril Hrubis
2026-03-19 16:03 ` [LTP] [PATCH 1/2] runtest/ltp-aidio.part4: Remove dio_sparse Cyril Hrubis
2026-03-19 17:38 ` Jan Kara
2026-03-20 7:28 ` Andrea Cervesato via ltp
2026-03-19 16:03 ` [LTP] [PATCH 2/2] runtest: ltp-aiodio.part2: Limit the maximal filesize Cyril Hrubis
2026-03-19 17:40 ` Jan Kara
2026-03-20 9:51 ` Cyril Hrubis [this message]
2026-03-20 9:54 ` Jan Kara
2026-03-26 14:50 ` [LTP] [PATCH 0/2] Cleanup of aiodio runtest files Cyril Hrubis
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=ab0Yn91oOC0TfVOV@yuki.lan \
--to=chrubis@suse.cz \
--cc=jack@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox