From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: Martin Doucha <mdoucha@suse.cz>, Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/2] aiodio: Set timeout 30 min
Date: Fri, 21 Jan 2022 14:43:55 +0100 [thread overview]
Message-ID: <cf761305-29fb-cd07-48f9-e6cea8f0cd7a@suse.com> (raw)
In-Reply-To: <5988d540-ce29-d210-365e-7e5efa91b547@suse.cz>
[-- Attachment #1.1: Type: text/plain, Size: 895 bytes --]
I agree with Martin that some tests in the aiodio testing suite should
handle default value a bit better. To reduce the amount of memory/time
required by manual execution with default values could be a task for the
next future.
On 1/21/22 14:38, Martin Doucha wrote:
> On 21. 01. 22 14:33, Petr Vorel wrote:
>>> Hi,
>>> only dio_sparse really needs higher timeout because we use it for a slow
>>> stress test in a runfile. dio_read should get a lower default number of
>>> child processes instead (8 or 16 to keep the default memory requirements
>>> under 512MB).
>> Thanks!
>>
>> I also noticed dio_read, but as you pointed out it's already fixed by
>> f3caabe44c ("Reduce memory footprint of the dio_read test")
> Runfile usage is fixed but running the program manually with default
> setting would still result in extreme memory use. We should make the
> defaults more sensible as well.
>
[-- Attachment #1.2: Type: text/html, Size: 1502 bytes --]
[-- Attachment #2: Type: text/plain, Size: 60 bytes --]
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-21 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 10:30 [LTP] [PATCH 2/2] aiodio: Set timeout 30 min Petr Vorel
2022-01-21 10:38 ` Cyril Hrubis
2022-01-21 12:02 ` Martin Doucha
2022-01-21 13:33 ` Petr Vorel
2022-01-21 13:38 ` Martin Doucha
2022-01-21 13:43 ` Andrea Cervesato via ltp [this message]
2022-01-21 13:54 ` Petr Vorel
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=cf761305-29fb-cd07-48f9-e6cea8f0cd7a@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=mdoucha@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox