All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Dave Gordon <david.s.gordon@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: refactor i915_gem_object_pin_map()
Date: Tue, 17 May 2016 10:22:51 +0100	[thread overview]
Message-ID: <573AE2EB.6030704@linux.intel.com> (raw)
In-Reply-To: <1463411944-13533-1-git-send-email-david.s.gordon@intel.com>


On 16/05/16 16:19, 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)
>
> v3:
>      Add page count to debug messages (Chris Wilson)
>      Convert WARN_ON() to GEM_BUG_ON()
>
> 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 | 59 ++++++++++++++++++++++++++---------------
>   1 file changed, 38 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index aff386e..bbec429 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -2398,6 +2398,43 @@ 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 sg_table *sgt = obj->pages;
> +	struct sg_page_iter sg_iter;
> +	struct page **pages;
> +	unsigned long i = 0;
> +	void *addr = NULL;

Looks like this does not need to be initialized?

> +
> +	/* A single page can always be kmapped */
> +	if (n_pages == 1)
> +		return kmap(sg_page(sgt->sgl));
> +
> +	pages = drm_malloc_gfp(n_pages, sizeof(*pages), GFP_TEMPORARY);
> +	if (pages == NULL) {
> +		DRM_DEBUG_DRIVER("Failed to get space for %lu pointers\n",
> +				 n_pages);

Not terribly important but I think this is too low level functions to 
have debug logging. It will not add a lot of useful information, no call 
stack etc. And the callers are probably handling failures already and 
they would propagate somewhere from where it is already reported.

> +		return NULL;
> +	}
> +
> +	for_each_sg_page(sgt->sgl, &sg_iter, sgt->nents, 0)
> +		pages[i++] = sg_page_iter_page(&sg_iter);
> +
> +	/* Check that we have the expected number of pages */
> +	GEM_BUG_ON(i != n_pages);
> +
> +	addr = vmap(pages, n_pages, 0, PAGE_KERNEL);
> +	if (addr == NULL)
> +		DRM_DEBUG_DRIVER("Failed to vmap %lu pages\n", n_pages);

Same here. I mean, the only potential argument could be that this will 
tell the real reason which is otherwise lost in the NULL return code, 
but I am not sure it is worth it since it is so unlikely it would happen.

> +
> +	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;
> @@ -2411,27 +2448,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);
>

Otherwise looks fine to me.

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-05-17  9:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 15:19 [PATCH 1/3] drm/i915: refactor i915_gem_object_pin_map() Dave Gordon
2016-05-16 15:19 ` [PATCH 2/3] drm/i915: optimise i915_gem_object_map() for small objects Dave Gordon
2016-05-16 15:19 ` [PATCH 3/3] Introduce & use new lightweight SGL iterators Dave Gordon
2016-05-16 15:19   ` Dave Gordon
2016-05-17 10:34   ` Tvrtko Ursulin
2016-05-17 10:34     ` [Intel-gfx] " Tvrtko Ursulin
2016-05-17 12:05     ` Dave Gordon
2016-05-19 17:27       ` Chris Wilson
2016-05-20  0:13         ` Dave Gordon
2016-05-16 16:01 ` ✗ Ro.CI.BAT: failure for series starting with [1/3] drm/i915: refactor i915_gem_object_pin_map() Patchwork
2016-05-17  9:22 ` Tvrtko Ursulin [this message]
2016-05-17 12:59   ` [PATCH 1/3] " Dave Gordon

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=573AE2EB.6030704@linux.intel.com \
    --to=tvrtko.ursulin@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 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.