From mboxrd@z Thu Jan 1 00:00:00 1970 From: Petr Vorel Date: Thu, 12 Sep 2019 19:01:27 +0200 Subject: [LTP] [PATCH] memcg_stress_test.sh: Respect LTP_TIMEOUT_MUL set by user In-Reply-To: <1568306840.3621.32.camel@suse.de> References: <20190830085036.GA27453@dell5510> <9e518589-9c98-1513-2c19-bae0268b8a81@arm.com> <20190830104609.GA9330@dell5510> <1568279073.3621.12.camel@suse.de> <20190912152820.GB1064@dell5510> <1568306840.3621.32.camel@suse.de> Message-ID: <20190912170127.GA3035@dell5510> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it 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