lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 26 Mar 2015 07:32:36 -0400
From:	Prarit Bhargava <prarit@...hat.com>
To:	John Stultz <john.stultz@...aro.org>
CC:	lkml <linux-kernel@...r.kernel.org>,
	Shuah Khan <shuahkh@....samsung.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Richard Cochran <richardcochran@...il.com>
Subject: Re: [PATCH 2/2] kselftests: timers: Reduce default runtime on inconsistency-check
 and set-timer-lat



On 03/25/2015 07:44 PM, John Stultz wrote:
> For the default run_timers target, the timers tests takes the
> majority of kselftests runtime.
> 
> So this patch reduces the default runtime for inconsistentcy-check
> and set-timer-lat, which reduced the runtime almost in half.
> 
> Before:	11m48.629s
> After:	6m47.723s
> 
> Cc: Shuah Khan <shuahkh@....samsung.com>
> Cc: Prarit Bhargava <prarit@...hat.com>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Richard Cochran <richardcochran@...il.com>
> Signed-off-by: John Stultz <john.stultz@...aro.org>
> Signed-off-by: John Stultz <john.stultz@...aro.org>
> ---
>  tools/testing/selftests/timers/inconsistency-check.c | 2 +-
>  tools/testing/selftests/timers/set-timer-lat.c       | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/timers/inconsistency-check.c b/tools/testing/selftests/timers/inconsistency-check.c
> index 578e423a..caf1bc9 100644
> --- a/tools/testing/selftests/timers/inconsistency-check.c
> +++ b/tools/testing/selftests/timers/inconsistency-check.c
> @@ -166,7 +166,7 @@ int main(int argc, char *argv[])
>  	int clockid, opt;
>  	int userclock = CLOCK_REALTIME;
>  	int maxclocks = NR_CLOCKIDS;
> -	int runtime = 30;
> +	int runtime = 10;
>  	struct timespec ts;
>  

Oops ... left everyone off :)

What was the reason that this was originally 30?  Or was that overkill?

P.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ