From: Caz Yokoyama <caz@caz-nuc.ra.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [igt PATCH 0/1] lib: igt@i915_suspend@shrink faster
Date: Wed, 20 Feb 2019 01:13:15 +0000 [thread overview]
Message-ID: <cover.1550624857.git.caz@caz-nuc.ra.intel.com> (raw)
igt@i915_suspend@shrink runs 25 sec instead of 90 sec on my NUC which has
2GB of memory. The child process which is created by igt_fork() updates
pinnable memory size, (*can_mlock). Parent process mlocks at the end of
"for loop" when the child process finds pinnable memory size in 4kb
boundary. This patch also reduces the chance of dying entire test process
because the parent process mclocks the memory where we already know it is
pinnable.
Incrementary mlocking small memory in addition to 3/4 of available memory
by the child process does not work because kernel finds the parent
process mlocks more memory than the child process and kills the parent
process.
Another big time consumer is igt_system_suspend_autoresume(). 15 sec of
delay is hard coded. It is too danger to reduce 15 sec because some of
test machines may fail by reducing delay time.
"gem_userptr_blits@mlocked-*" test also calls
intel_get_total_pinnable_mem(). I do not test them because they do not
finish within 30 min on my NUC without this patch.
Caz Yokoyama (1):
igt@i915_suspend@shrink faster
lib/intel_os.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.17.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-02-19 18:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 1:13 Caz Yokoyama [this message]
2019-02-19 19:05 ` [igt-dev] ✓ Fi.CI.BAT: success for lib: igt@i915_suspend@shrink faster Patchwork
2019-02-19 22:37 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-19 22:49 ` [igt-dev] ✓ Fi.CI.BAT: success for lib: igt@i915_suspend@shrink faster (rev2) Patchwork
2019-02-20 0:53 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-20 1:13 ` [igt-dev] [igt PATCH 1/1] igt@i915_suspend@shrink faster Caz Yokoyama
2019-02-19 22:21 ` [igt-dev] [PATCH i-g-t] lib: Incrementally mlock() Chris Wilson
2019-02-20 5:26 ` Ashutosh Dixit
2019-02-20 5:39 ` Ashutosh Dixit
2019-02-20 22:28 ` Caz Yokoyama
2019-02-26 17:42 ` [igt-dev] FW: " Yokoyama, Caz
2019-02-26 17:42 ` Chris Wilson
2019-02-26 20:34 ` Caz Yokoyama
2019-02-26 21:31 ` Chris Wilson
2019-02-27 0:40 ` Caz Yokoyama
2019-02-27 8:13 ` Chris Wilson
2019-02-20 3:14 ` [igt-dev] [igt PATCH 1/1] igt@i915_suspend@shrink faster Ashutosh Dixit
2019-02-26 17:56 ` [igt-dev] ✗ Fi.CI.BAT: failure for lib: igt@i915_suspend@shrink faster (rev3) Patchwork
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=cover.1550624857.git.caz@caz-nuc.ra.intel.com \
--to=caz@caz-nuc.ra.intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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