Intel-GFX Archive on lore.kernel.org
 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 2/2] drm/i915: Move stale context reaping to common i915_gem_context_create
Date: Wed, 5 Jul 2017 14:50:57 +0100	[thread overview]
Message-ID: <ddbd78ab-8228-aba5-6f14-47c3a236552b@linux.intel.com> (raw)
In-Reply-To: <20170705131820.20501-2-chris@chris-wilson.co.uk>


On 05/07/2017 14:18, Chris Wilson wrote:
> We need to reap the stale contexts for all new contexts, be they created
> by user in i915_gem_context_ioctl or from opening a new file in
> i915_gem_context_open. Both paths may be called very frequently
> accumulating many stale contexts before any worker has a chance to run
> and free their memory.
> 
> Fixes: 1acfc104cdf8 ("drm/i915: Enable rcu-only context lookups")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
>   drivers/gpu/drm/i915/i915_gem_context.c | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index 98d2ce98f467..c58a95c33c25 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -383,6 +383,10 @@ i915_gem_create_context(struct drm_i915_private *dev_priv,
>   
>   	lockdep_assert_held(&dev_priv->drm.struct_mutex);
>   
> +	/* Reap stale contexts */
> +	i915_gem_retire_requests(dev_priv);
> +	contexts_free(dev_priv);
> +
>   	ctx = __create_hw_context(dev_priv, file_priv);
>   	if (IS_ERR(ctx))
>   		return ctx;
> @@ -989,10 +993,6 @@ int i915_gem_context_create_ioctl(struct drm_device *dev, void *data,
>   	if (ret)
>   		return ret;
>   
> -	/* Reap stale contexts */
> -	i915_gem_retire_requests(dev_priv);
> -	contexts_free(dev_priv);
> -
>   	ctx = i915_gem_create_context(dev_priv, file_priv);
>   	mutex_unlock(&dev->struct_mutex);
>   	if (IS_ERR(ctx))
> 

Can't make myself concerned about the context creation slowdown with 
this solution. I guess it highlights the same old RCU/delayed worker 
issues, but it could be an option to somehow generalize these things 
based on some threshold, like:

maybe_pruge_deleted_contexts()
{
	if (nr_contexts_on_free_list > some_threshold) {
		retire...
		free...
	}
}

Anyway:

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:[~2017-07-05 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 13:18 [PATCH 1/2] drm/i915: Check new context against kernel_context after reporting an error Chris Wilson
2017-07-05 13:18 ` [PATCH 2/2] drm/i915: Move stale context reaping to common i915_gem_context_create Chris Wilson
2017-07-05 13:50   ` Tvrtko Ursulin [this message]
2017-07-05 14:08     ` Chris Wilson
2017-07-05 13:37 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Check new context against kernel_context after reporting an error Patchwork
2017-07-05 13:46 ` [PATCH 1/2] " Tvrtko Ursulin

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=ddbd78ab-8228-aba5-6f14-47c3a236552b@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