On Tue, 09 Oct 2012 23:16:02 +0100, Chris Wilson <[email protected]> 
wrote:
> On Tue,  9 Oct 2012 22:50:48 +0200, Daniel Vetter <[email protected]> 
> wrote:
> > The obj->pages to obj->pages->sgl rework introduced this helper, but
> > it doesn't actually work for n >= SG_MAX_SINGLE_ALLOC.
> > 
> > For simplicity (and since right now I seem to be too stupid to see
> > the bug), let's just grab the right page with a for_each_sg loop.
> > 
> > This is exercised by the improved hangman tests and the gem_exec_big
> > test in i-g-t.
> > 
> > v2: Compared to v1, don't try to be clever since I seemingly only
> > manage to prove that I'm not clever.
> 
> Only I expect that loop to show up on profiles even higher than the
> sg_next() from pwrite. :|
> 
> I expect it to have a measureable impact upon relocation throughput,
> so I should measure it...
> -Chris
> 
> -- 
> Chris Wilson, Intel Open Source Technology Centre
> _______________________________________________
> Intel-gfx mailing list
> [email protected]
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
From: Chris Wilson <[email protected]>
Subject: Re: [PATCH] drm/i915: fixup i915_gem_object_get_page inline helper
To: Daniel Vetter <[email protected]>, Intel Graphics Development 
<[email protected]>
Cc: Daniel Vetter <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]> 
<[email protected]>

On Tue,  9 Oct 2012 22:50:48 +0200, Daniel Vetter <[email protected]> 
wrote:
> The obj->pages to obj->pages->sgl rework introduced this helper, but
> it doesn't actually work for n >= SG_MAX_SINGLE_ALLOC.
> 
> For simplicity (and since right now I seem to be too stupid to see
> the bug), let's just grab the right page with a for_each_sg loop.
> 
> This is exercised by the improved hangman tests and the gem_exec_big
> test in i-g-t.
> 
> v2: Compared to v1, don't try to be clever since I seemingly only
> manage to prove that I'm not clever.
> 
> Signed-off-by: Daniel Vetter <[email protected]>

Looks like my worries are baseless. It can always be attacked latter if
need be. I'd still like to know what the mistake was...

Reviewed-by: Chris Wilson <[email protected]>
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to