From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] runtest/ltp-aiodio.part4: Remove duplicate entries
Date: Tue, 7 Jan 2025 11:43:06 +0100 [thread overview]
Message-ID: <Z30FOs2ckQTxEYLl@yuki.lan> (raw)
In-Reply-To: <20250106141635.GA323533@pevik>
Hi!
> @Cyril? If relevant maybe we should just document it. Does it apply to all
> duplicates? I wonder if it makes sense to run whole runset for 45 min when we
> are testing something mainline does not care about it's performance.
Well the ltp-aiodio.part4 is a stress test that iterates between
different I/O stress tests. Stress tests by definition must run for some
time to be useful, the question is for how long these should be run and
for that there is no clear answer I'm afraid.
The dirty and dio_sparse are interleaved because dirty tries to fill in
the page cache with dirty pages before each dio_sparse iteration. The
dio_sparse then creates a sparse file and checks that we correctly read
zeroes all the time while other processes write zeroes to the sparse
file. It may make sense to merge the dirty.c into the dio_sparse.c so
that it's executed at the start of the test and then possibly eliminate
one block of the dio_sparse tests.
We may as well get rid of the multiple lines in the runtest file by
passing -i option since these tests were converted into the new test
library. But over all I wouldn't vote for reducing the runtime for these
tests as drastically as you proposed.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-01-07 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 14:04 [LTP] [PATCH 1/1] runtest/ltp-aiodio.part4: Remove duplicate entries Petr Vorel
2025-01-06 14:12 ` Andrea Cervesato via ltp
2025-01-06 14:16 ` Petr Vorel
2025-01-07 10:43 ` Cyril Hrubis [this message]
2025-01-07 11:33 ` Andrea Cervesato via ltp
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=Z30FOs2ckQTxEYLl@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.