From: Caz Yokoyama <Caz.Yokoyama@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/1] i915_pm_rpm: gem-execbuf-stress-extra-wait faster
Date: Tue, 05 Mar 2019 15:22:06 -0800 [thread overview]
Message-ID: <678cb1a5caa56b23e92c338ccc4c07e08df999bb.camel@intel.com> (raw)
In-Reply-To: <155180654478.27405.14279936406391255294@skylake-alporthouse-com>
On Tue, 2019-03-05 at 17:22 +0000, Chris Wilson wrote:
> Quoting Caz Yokoyama (2019-03-06 00:06:55)
> > Less iterate because WAIT_EXTRA adds extra 5 sec delay for each
> > iteration.
> > This test is similar to gem-execbuf-stress except for WAIT_EXTRA.
> > It runs 86 sec. while gem-execbuf-stress runs 38 sec.
> > i.e. 38s + iteration(rounds,10) * 5s = 88s
>
> Why does it wait for 5s? There's no second stage to runtime suspend,
> but
> if there was, add a debug interface to force it.
I believe no because teardown_environment() is the onlye statement
after igt_subtest("gem-execbuf-stress-extra-wait").
> Something else that can be employed to speed up this test would be
> igt_drop_caches_set(DROP_IDLE) (before waiting for runtime suspend).
Yes, it does speed up to 56sec from 88sec. Not only gem-execbuf-stress-
extra-wait, but also other 2 tests speed up. For example, gem-execbuf-
stress speed up to 9sec from 38sec. Thank you.
How do you want to have patches? Only igt_drop_caches_set(DROP_IDLE)?
Both igt_drop_caches_set(DROP_IDLE) and rounds / 2 in a single patch?
Separate 2 patches?
-caz
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-05 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 0:06 [igt-dev] [PATCH i-g-t 1/1] i915_pm_rpm: gem-execbuf-stress-extra-wait faster Caz Yokoyama
2019-03-05 17:22 ` Chris Wilson
2019-03-05 23:22 ` Caz Yokoyama [this message]
2019-03-05 23:29 ` Chris Wilson
2019-03-07 18:21 ` Caz Yokoyama
2019-03-07 20:57 ` Chris Wilson
2019-03-05 19:07 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/1] " Patchwork
2019-03-05 22:59 ` [igt-dev] ✓ Fi.CI.IGT: " 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=678cb1a5caa56b23e92c338ccc4c07e08df999bb.camel@intel.com \
--to=caz.yokoyama@intel.com \
--cc=chris@chris-wilson.co.uk \
--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