From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Remove i915_vma_create from VMA API
Date: Mon, 16 Jan 2017 14:01:43 +0200 [thread overview]
Message-ID: <1484568103.3521.16.camel@linux.intel.com> (raw)
In-Reply-To: <20170116094946.8244-2-chris@chris-wilson.co.uk>
On ma, 2017-01-16 at 09:49 +0000, Chris Wilson wrote:
> With the introduce of i915_vma_instance() for obtaining the VMA
> singleton for a (obj, vm, view) tuple, we can remove the
> i915_vma_create() in favour of a single entry point. We do incur a
> lookup onto an empty tree, but the i915_vma_create() were being called
> infrequently and during initialisation, so the small overhead is
> negligible.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
<SNIP>
> struct i915_vma *
> -i915_vma_create(struct drm_i915_gem_object *obj,
> - struct i915_address_space *vm,
> - const struct i915_ggtt_view *view);
> -
> -struct i915_vma *
> i915_vma_lookup(struct drm_i915_gem_object *obj,
> struct i915_address_space *vm,
> const struct i915_ggtt_view *view);
I'd say our de-facto is to drop "i915_" prefix from locals.
Would add to the code understandability, but anyway;
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
next prev parent reply other threads:[~2017-01-16 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 9:49 [PATCH 1/2] drm/i915: Rename some warts in the VMA API Chris Wilson
2017-01-16 9:49 ` [PATCH 2/2] drm/i915: Remove i915_vma_create from " Chris Wilson
2017-01-16 12:01 ` Joonas Lahtinen [this message]
2017-01-16 10:17 ` [PATCH 1/2] drm/i915: Rename some warts in the " Chris Wilson
2017-01-16 11:34 ` Joonas Lahtinen
2017-01-16 12:24 ` ✗ Fi.CI.BAT: warning for series starting with [1/2] " 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=1484568103.3521.16.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.