All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Subject: [RFC 0/4] Shrinker tweaks/fixes?
Date: Thu,  3 Jan 2019 12:23:25 +0000	[thread overview]
Message-ID: <20190103122329.19948-1-tvrtko.ursulin@linux.intel.com> (raw)

From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

A few patches to put my money where my mouth is regarding review comments where
I am suggesting to split up a patch for safety.

This ends one step short compared to the parent
(https://patchwork.freedesktop.org/patch/273593/) by omitting the final
mutex_lock_nested step, in order to see what kind of lockdep traces we get, or
if none for that to be a clear sign we need better tests.

Tvrtko Ursulin (4):
  drm/i915: Reduce recursive mutex locking from the shrinker
  drm/i915: Fix timeout handling in i915_gem_shrinker_vmap
  drm/i915: Return immediately if trylock fails for direct-reclaim
  drm/i915: Remove trylock-looping from the shrinker

 drivers/gpu/drm/i915/i915_drv.h          | 11 ++---
 drivers/gpu/drm/i915/i915_gem_shrinker.c | 51 +++++++++++-------------
 2 files changed, 29 insertions(+), 33 deletions(-)

-- 
2.19.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2019-01-03 12:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 12:23 Tvrtko Ursulin [this message]
2019-01-03 12:23 ` [RFC 1/4] drm/i915: Reduce recursive mutex locking from the shrinker Tvrtko Ursulin
2019-01-03 12:29   ` Chris Wilson
2019-01-03 13:09     ` Tvrtko Ursulin
2019-01-03 12:23 ` [RFC 2/4] drm/i915: Fix timeout handling in i915_gem_shrinker_vmap Tvrtko Ursulin
2019-01-03 12:23 ` [RFC 3/4] drm/i915: Return immediately if trylock fails for direct-reclaim Tvrtko Ursulin
2019-01-03 12:23 ` [RFC 4/4] drm/i915: Remove trylock-looping from the shrinker Tvrtko Ursulin
2019-01-03 12:56   ` Chris Wilson
2019-01-03 13:10     ` Tvrtko Ursulin
2019-01-03 12:45 ` ✗ Fi.CI.CHECKPATCH: warning for Shrinker tweaks/fixes? Patchwork
2019-01-03 12:47 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-03 13:06 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-03 14:54 ` ✗ Fi.CI.IGT: failure " 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=20190103122329.19948-1-tvrtko.ursulin@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.