intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Retire before attempting to evict from the active lists
Date: Mon, 12 Dec 2016 11:58:24 +0000	[thread overview]
Message-ID: <48c66609-6cd2-07aa-4fec-ed60b2bc8fe5@linux.intel.com> (raw)
In-Reply-To: <20161209150555.602-1-chris@chris-wilson.co.uk>


On 09/12/2016 15:05, Chris Wilson wrote:
> Some object retain an extra pin whilst they are active (e.g. contexts).
> This excludes them from being considered for eviction unless we idle the
> GPU. If before we look at the active list, before we retire we can
> hopefully remove a few excess pins and reduce the amount of searching
> required.
>
> v2: Similar principle applies to evict_for_vma
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>  drivers/gpu/drm/i915/i915_gem_evict.c | 17 ++++++++++++++++-
>  1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_evict.c b/drivers/gpu/drm/i915/i915_gem_evict.c
> index a3f7f1ca6f21..689338e22ba8 100644
> --- a/drivers/gpu/drm/i915/i915_gem_evict.c
> +++ b/drivers/gpu/drm/i915/i915_gem_evict.c
> @@ -130,7 +130,14 @@ i915_gem_evict_something(struct i915_address_space *vm,
>  				    start, end,
>  				    flags & PIN_HIGH ? DRM_MM_INSERT_HIGH : 0);
>
> -	if (flags & PIN_NONBLOCK)
> +	/* Retire before we search the active list. Although we have
> +	 * reasonable accuracy in our retirement lists, we may have
> +	 * a stray pin (preventing eviction) that can only be resolved by
> +	 * retiring.
> +	 */
> +	if (!(flags & PIN_NONBLOCK))
> +		i915_gem_retire_requests(dev_priv);
> +	else
>  		phases[1] = NULL;
>
>  search_again:
> @@ -236,6 +243,14 @@ int i915_gem_evict_for_vma(struct i915_vma *target, unsigned int flags)
>  	lockdep_assert_held(&target->vm->i915->drm.struct_mutex);
>  	trace_i915_gem_evict_vma(target, flags);
>
> +	/* Retire before we search the active list. Although we have
> +	 * reasonable accuracy in our retirement lists, we may have
> +	 * a stray pin (preventing eviction) that can only be resolved by
> +	 * retiring.
> +	 */
> +	if (!(flags & PIN_NONBLOCK))
> +		i915_gem_retire_requests(target->vm->i915);
> +
>  	check_color = target->vm->mm.color_adjust;
>  	if (check_color) {
>  		/* Expand search to cover neighbouring guard pages (or lack!) */
>

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Regards,

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

  reply	other threads:[~2016-12-12 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09 13:42 [PATCH] drm/i915: Retire before attempting to evict from the active lists Chris Wilson
2016-12-09 15:05 ` [PATCH v2] " Chris Wilson
2016-12-12 11:58   ` Tvrtko Ursulin [this message]
2016-12-13 11:19     ` Chris Wilson

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=48c66609-6cd2-07aa-4fec-ed60b2bc8fe5@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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).