All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Defer context state allocation for legacy ring submission
Date: Thu, 27 Apr 2017 13:56:35 +0300	[thread overview]
Message-ID: <1493290595.7266.20.camel@linux.intel.com> (raw)
In-Reply-To: <20170427104651.22394-1-chris@chris-wilson.co.uk>

On to, 2017-04-27 at 11:46 +0100, Chris Wilson wrote:
> Almost from the outset for execlists, we used deferred allocation of the
> logical context and rings. Then we ported the infrastructure for pinning
> contexts back to legacy, and so now we are able to also implement
> deferred allocation for context objects prior to first use on the legacy
> submission.
> 
> v2: We still need to differentiate between legacy engines, Joonas is
> fixing that but I want this first ;) (Joonas)
> 
> 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>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>

You went the extra mile to reduce the if-claus too, so;

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-04-27 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27 10:37 [PATCH] drm/i915: Defer context state allocation for legacy ring submission Chris Wilson
2017-04-27 10:46 ` [PATCH v2] " Chris Wilson
2017-04-27 10:56   ` Joonas Lahtinen [this message]
2017-04-27 11:06 ` ✓ Fi.CI.BAT: success for drm/i915: Defer context state allocation for legacy ring submission (rev2) Patchwork
2017-04-27 11:44   ` 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=1493290595.7266.20.camel@linux.intel.com \
    --to=joonas.lahtinen@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 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.