From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 03/10] ksm: Add max_runtime to tests
Date: Mon, 5 Sep 2022 18:14:23 +0200 [thread overview]
Message-ID: <YxYgX51MTYG1U3z8@pevik> (raw)
In-Reply-To: <fb93f3bd-1a22-6a1d-c0ed-01eba39121bb@suse.cz>
> On 31. 08. 22 14:50, Cyril Hrubis wrote:
> > Hi!
> > > Alternatively, we could measure 1 full ksmd scan in setup() and then set
> > > max_runtime dynamically. Each call of create_same_memory() would need
> > > roughly 16 scan times. Time spent in ksm_child_memset() is included in
> > > that estimate.
> > That sounds good as well, but I would still set the .max_runtime to
> > rough guess in tst_test structure and then adjusted it in the test
> > setup().
> The current patch is a good enough guess for ~2-4GB machines. Or do you want
> to target bigger machines by default?
I guess it'd be safer to expect machines with bigger memory.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-05 16:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 13:49 [LTP] [PATCH 00/10] Max_runtime and other minor fixes Martin Doucha
2022-08-30 13:49 ` [LTP] [PATCH 01/10] syscalls/pty06: Add CVE reference Martin Doucha
2022-08-30 14:40 ` Cyril Hrubis
2022-08-30 13:49 ` [LTP] [PATCH 02/10] cve-2017-2671: Increase max_runtime Martin Doucha
2022-08-30 14:40 ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 03/10] ksm: Add max_runtime to tests Martin Doucha
2022-08-30 14:49 ` Cyril Hrubis
2022-08-31 12:45 ` Martin Doucha
2022-08-31 12:50 ` Cyril Hrubis
2022-08-31 12:54 ` Martin Doucha
2022-09-05 16:14 ` Petr Vorel [this message]
2022-09-09 8:28 ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 04/10] ioctl_sg01: Set unlimited max_runtime Martin Doucha
2022-08-30 15:16 ` Cyril Hrubis
2022-08-30 15:23 ` Martin Doucha
2022-08-30 18:38 ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 05/10] csf_bandwidth01: Add max_runtime Martin Doucha
2022-08-30 15:30 ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 06/10] copy_file_range01: " Martin Doucha
2022-08-31 8:21 ` Petr Vorel
2022-08-31 9:06 ` Cyril Hrubis
2022-08-31 12:18 ` Petr Vorel
2022-08-31 9:06 ` Martin Doucha
2022-08-31 9:25 ` Cyril Hrubis
2022-08-31 12:19 ` Petr Vorel
2022-08-31 9:22 ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 07/10] perf_event_open02: " Martin Doucha
2022-08-31 8:23 ` Petr Vorel
2022-08-31 10:07 ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 08/10] readahead02: " Martin Doucha
2022-08-31 9:29 ` Petr Vorel
2022-08-31 11:29 ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 09/10] request_key03: " Martin Doucha
2022-08-31 9:45 ` Petr Vorel
2022-08-31 9:47 ` Petr Vorel
2022-08-31 12:24 ` Cyril Hrubis
2022-08-30 13:50 ` [LTP] [PATCH 10/10] sendfile09: " Martin Doucha
2022-08-31 9:48 ` Petr Vorel
2022-08-31 12:59 ` Jan Stancek
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=YxYgX51MTYG1U3z8@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@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