From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] i915/gem_tiled_swapping: Tweak mlocked size
Date: Wed, 4 Sep 2019 09:47:39 +0300 [thread overview]
Message-ID: <20190904064739.GD22095@intel.intel> (raw)
In-Reply-To: <20190903193151.3132-1-chris@chris-wilson.co.uk>
Hi Chris,
On Tue, Sep 03, 2019 at 08:31:51PM +0100, Chris Wilson wrote:
> On my systems with lots of memdebug enabled, we would hit the oomkiller
> 90% of the time during the initial mlock prior to allocating any objects
> (and about 20% of the time lockup / panic). Tweak the target allocation
> sizes, and include a few more breadcrumbs tracing the allocations so
> that we can reliably start the tests. We still do hit our shrinker and
> even the oom notifier, so still achieving its goal of exercising low
> memory and swap pressure.
>
> To slightly compensate for the reduced mempressure (albeit we do not
> remove the swapping, the raison d'etre of the test), we increase the
> number of threads to force the system to reuse active fences, making it
> more stressful on the fence code.
Ah... OK :)
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Andi Shyti <andi.shyti@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-04 6:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 4:15 [PATCH i-g-t 1/6] lib: Fix gem_measure_ring_inflight Chris Wilson
2019-09-02 4:15 ` [PATCH i-g-t 2/6] i915/gem_ctx_shared: Prebind both context images Chris Wilson
2019-09-03 13:59 ` [PATCH i-g-t] " Chris Wilson
2019-09-03 15:25 ` [igt-dev] [PATCH i-g-t 2/6] " Andi Shyti
2019-09-02 4:15 ` [PATCH i-g-t 3/6] i915/gem_tiled_swapped: Tweak mlocked size Chris Wilson
2019-09-03 15:32 ` [igt-dev] " Andi Shyti
2019-09-03 19:31 ` [PATCH i-g-t] i915/gem_tiled_swapping: " Chris Wilson
2019-09-04 6:47 ` Andi Shyti [this message]
2019-09-02 4:15 ` [PATCH i-g-t 4/6] Add i915/gem_ctx_persistence Chris Wilson
2019-09-03 17:50 ` [igt-dev] " Andi Shyti
2019-09-02 4:15 ` [PATCH i-g-t 5/6] i915/gem_mocs_settings: Fudge gen11:vcs2 mocs register base Chris Wilson
2019-09-02 4:15 ` [PATCH i-g-t 6/6] i915/gem_exec_balancer: Beware the migratory fence Chris Wilson
2019-09-03 12:53 ` [PATCH i-g-t 1/6] lib: Fix gem_measure_ring_inflight Andi Shyti
2019-09-03 14:40 ` ✓ Fi.CI.BAT: success for i915/gem_ctx_shared: Prebind both context images Patchwork
2019-09-03 18:29 ` ✓ 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=20190904064739.GD22095@intel.intel \
--to=andi.shyti@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@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;
as well as URLs for NNTP newsgroup(s).