public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Dave Gordon <david.s.gordon@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] drm/i915: refactor i915_gem_object_pin_map()
Date: Thu, 21 Apr 2016 11:09:32 +0300	[thread overview]
Message-ID: <1461226172.4381.30.camel@linux.intel.com> (raw)
In-Reply-To: <1461159055-11991-1-git-send-email-david.s.gordon@intel.com>

On ke, 2016-04-20 at 14:30 +0100, 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(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 6ce2c31..5344b6d 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -2396,6 +2396,42 @@ static void i915_gem_object_free_mmap_offset(struct drm_i915_gem_object *obj)
>  	return 0;
>  }
>  
> +/* The 'mapping' part of i915_gem_object_pin_map() below */
> +static void *i915_gem_object_map(const struct drm_i915_gem_object *obj)
> +{
> +	unsigned long n_pages = obj->base.size >> PAGE_SHIFT;
> +	struct scatterlist *sg = obj->pages->sgl;
> +	struct sg_page_iter sg_iter;
> +	struct page **pages;
> +	unsigned long i = 0;
> +	void *addr = NULL;
> +
> +	/* A single page can always be kmapped */
> +	if (n_pages == 1)
> +		return kmap(sg_page(sg));
> +
> +	pages = drm_malloc_gfp(n_pages, sizeof(*pages), GFP_TEMPORARY);
> +	if (pages == NULL) {
> +		DRM_DEBUG_DRIVER("Failed to get space for pages\n");
> +		return NULL;
> +	}
> +
> +	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);
> +
> +	if (addr == NULL)
> +		DRM_DEBUG_DRIVER("Failed to vmap pages\n");
> +
	This kind of construct is used elsewhere, too.

	if (WARN_ON(i != n_pages)) {
		DRM_DEBUG_DRIVER("Failed to vmap pages\n");
		goto out;
	}

	addr = vmap(pages, n_pages, 0, PAGE_KERNEL);

out:
> +	drm_free_large(pages);
> +
> +	return addr;
> +}
> +
> +/* get, pin, and map the pages of the object into kernel space */
>  void *i915_gem_object_pin_map(struct drm_i915_gem_object *obj)
>  {
>  	int ret;
> @@ -2409,27 +2445,7 @@ void *i915_gem_object_pin_map(struct drm_i915_gem_object *obj)
>  	i915_gem_object_pin_pages(obj);
>  
>  	if (obj->mapping == NULL) {
> -		struct page **pages;
> -
> -		pages = NULL;
> -		if (obj->base.size == PAGE_SIZE)
> -			obj->mapping = kmap(sg_page(obj->pages->sgl));
> -		else
> -			pages = drm_malloc_gfp(obj->base.size >> PAGE_SHIFT,
> -					       sizeof(*pages),
> -					       GFP_TEMPORARY);
> -		if (pages != NULL) {
> -			struct sg_page_iter sg_iter;
> -			int n;
> -
> -			n = 0;
> -			for_each_sg_page(obj->pages->sgl, &sg_iter,
> -					 obj->pages->nents, 0)
> -				pages[n++] = sg_page_iter_page(&sg_iter);
> -
> -			obj->mapping = vmap(pages, n, 0, PAGE_KERNEL);
> -			drm_free_large(pages);
> -		}
> +		obj->mapping = i915_gem_object_map(obj);
>  		if (obj->mapping == NULL) {
>  			i915_gem_object_unpin_pages(obj);
>  			return ERR_PTR(-ENOMEM);
-- 
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

      parent reply	other threads:[~2016-04-21  8:08 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     ` [PATCH v2 1/2] drm/i915: refactor i915_gem_object_pin_map() Dave Gordon
2016-04-21  8:09     ` Joonas Lahtinen [this message]

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=1461226172.4381.30.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox