From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] drm/i915: refactor i915_gem_object_pin_map()
Date: Wed, 20 Apr 2016 14:57:58 +0100 [thread overview]
Message-ID: <57178AE6.40905@intel.com> (raw)
In-Reply-To: <1461159055-11991-1-git-send-email-david.s.gordon@intel.com>
On 20/04/16 14:30, Dave Gordon wrote:
> The recently-added i915_gem_object_pin_map() can be further optimised
> for "small" objects. To facilitate this, and simplify the error paths
> before adding the new code, this patch pulls out the "mapping" part of
> the operation (involving local allocations which must be undone before
> return) into its own subfunction.
>
> The next patch will then insert the new optimisation into the middle of
> the now-separated subfunction.
>
> This reorganisation will probably not affect the generated code, as the
> compiler will most likely inline it anyway, but it makes the logical
> structure a bit clearer and easier to modify.
>
> v2:
> Restructure loop-over-pages & error check (Chris Wilson)
>
> Signed-off-by: Dave Gordon <david.s.gordon@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 58 ++++++++++++++++++++++++++---------------
> 1 file changed, 37 insertions(+), 21 deletions(-)
[snip]
> + for_each_sg_page(sg, &sg_iter, n_pages, 0)
> + pages[i++] = sg_page_iter_page(&sg_iter);
> +
> + /* Check that we have the expected number of pages */
> + if (!WARN_ON(i != n_pages))
> + addr = vmap(pages, n_pages, 0, PAGE_KERNEL);
Well actually the shorter loop and the subsequent check didn't turn out
too ugly; the only thing I don't much like is if (!WARN_ON(...)),
because I think in general that code should still function if WARN() and
similar macros are #defined to empty loops. But WARN_ON() has to be
defined to return (the truth-value of) its parameter even if it doesn't
print anything, so it's not that bad.
OTOH, while looking at this loop, I worked out a better page iterator,
so I'll post that in a little while :)
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-20 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 17:40 [PATCH 1/2] drm/i915: refactor i915_gem_object_pin_map() Dave Gordon
2016-04-19 17:40 ` [PATCH 2/2] drm/i915: optimise i915_gem_object_map() for small objects Dave Gordon
2016-04-19 19:50 ` [PATCH 1/2] drm/i915: refactor i915_gem_object_pin_map() Chris Wilson
2016-04-20 9:39 ` Dave Gordon
2016-04-20 13:30 ` [PATCH v2 " Dave Gordon
2016-04-20 13:30 ` [PATCH v2 2/2] drm/i915: optimise i915_gem_object_map() for small objects Dave Gordon
2016-04-20 13:57 ` Dave Gordon [this message]
2016-04-21 8:09 ` [PATCH v2 1/2] drm/i915: refactor i915_gem_object_pin_map() Joonas Lahtinen
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=57178AE6.40905@intel.com \
--to=david.s.gordon@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.