From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] memcg_stress_test.sh: Respect LTP_TIMEOUT_MUL set by user
Date: Thu, 12 Sep 2019 19:01:27 +0200 [thread overview]
Message-ID: <20190912170127.GA3035@dell5510> (raw)
In-Reply-To: <1568306840.3621.32.camel@suse.de>
Hi Clements,
> On Thu, 2019-09-12 at 17:28 +0200, Petr Vorel wrote:
> > Hi,
> > LTP_TIMEOUT_MUL is only for user, LTP_TIMEOUT_MUL_MIN is only for
> > library.
> > It's similar to way which is used in virt_lib.sh
> > (VIRT_PERF_THRESHOLD_MIN).
> Agree that LTP_TIMEOUT_MUL is for the user and the initial timeout
> value comes from library.
> I only say, that a LTP_TIMEOUT_MUL_MIN isn't needed from my
> perspective, if we allow to set a absolute timeout value like
> TST_TIMEOUT (as we already do in c). Because it has the same effect,
> setting a minimum timeout value which the user cannot reduce.
OK, replace LTP_TIMEOUT_MUL_MIN with TST_TIMEOUT set by test, make sense.
Thanks for a hint :).
> > See
> > https://patchwork.ozlabs.org/patch/1155460/
> > I'll probably sent this patch today although so you can base the work
> > on it.
> > Is that ok?
> sure it is.
:)
Kind regards,
Petr
prev parent reply other threads:[~2019-09-12 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 18:11 [LTP] [PATCH] memcg_stress_test.sh: Respect LTP_TIMEOUT_MUL set by user Petr Vorel
2019-08-30 2:39 ` Li Wang
2019-08-30 8:50 ` Petr Vorel
2019-08-30 9:07 ` Cristian Marussi
2019-08-30 10:46 ` Petr Vorel
2019-09-02 2:34 ` Li Wang
2019-09-12 9:04 ` Clemens Famulla-Conrad
2019-09-12 9:33 ` Cristian Marussi
2019-09-12 9:34 ` Li Wang
2019-09-12 9:51 ` Clemens Famulla-Conrad
2019-09-12 9:55 ` Cristian Marussi
2019-09-12 10:16 ` Clemens Famulla-Conrad
2019-09-12 15:28 ` Petr Vorel
2019-09-12 16:47 ` Clemens Famulla-Conrad
2019-09-12 17:01 ` Petr Vorel [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=20190912170127.GA3035@dell5510 \
--to=pvorel@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.