From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Reduce needed memory by the dio_read test
Date: Fri, 21 Jan 2022 10:19:55 +0100 [thread overview]
Message-ID: <Yep6u4N+phjB32Xd@pevik> (raw)
In-Reply-To: <Yep1Wm84sKzl3iB6@pevik>
Hi all,
...
> > But I'm not sure about the -s 5M part, the file size was always 128MB
> > before and reducing it to 5M sounds like too much. On my machine that
> > reduces the testing time from about one minute to a few seconds, that sounds
> > like change that is too radical without further explanation. If we want
> > to run the test with smaller file size I would go for 64M, that reduces
> > the runtime to half without reducing the changes for triggering a bug
> > too much.
> Good catch.
> I'm also going to verify ADSP075 dio_sparse -w 518192k -s 518192k -n 1000
> from ltp-aiodio.part2. Cyril's suggestion is to use '-n 1' to emulate
> only single children in previous implementation.
No, this is wrong. Also the issue can be just a timeout.
ADSP074 (uses -n 512) runs framework ~3.5 min, ADSP075 (uses -n 1000) gets killed
by LTP timeout. Do we want to increase tst_test.timeout for test?
Am I correct that we cannot increase based on particular input (for particular
getopt value) as we cannot later update results.timeout during run?
Kind regards,
Petr
> Kind regards,
> Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-21 9:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 15:04 [LTP] [PATCH v1] Reduce needed memory by the dio_read test Andrea Cervesato
2022-01-20 15:07 ` Martin Doucha
2022-01-20 15:31 ` Cyril Hrubis
2022-01-21 8:56 ` Petr Vorel
2022-01-21 9:19 ` Petr Vorel [this message]
2022-01-21 9:27 ` Cyril Hrubis
2022-01-21 9:30 ` Cyril Hrubis
2022-01-21 10:23 ` Petr Vorel
2022-01-21 9:02 ` 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=Yep6u4N+phjB32Xd@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@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 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.