On Wed, Jan 25, 2012 at 09:40, Jose Fonseca wrote:
> Thanks Stephane. Much better.
>
> I still think the flush flags semantics are quite confusing, but the problem
> comes from way before this change. Take e.g. the chunk:
>
> + /* don't prepare if we only are flushing the backend */
> +
Thanks Stephane. Much better.
I still think the flush flags semantics are quite confusing, but the problem
comes from way before this change. Take e.g. the chunk:
+ /* don't prepare if we only are flushing the backend */
+ if (!(flags & DRAW_FLUSH_BACKEND))
+ draw->pt.frontend
Please ignore that, I forgot to replace it. That said the rest has
been updated :)
Stéphane
2012/1/24 Stéphane Marchesin :
> I picked those draw changes from Jakob's branch. I discarded the first two
> commits (regresses glest) and the last one (i915g specific, works around a bug
> that was alre
I picked those draw changes from Jakob's branch. I discarded the first two
commits (regresses glest) and the last one (i915g specific, works around a bug
that was already fixed properly in git). Gives me a ~10% perf improvement in
state-intensive apps like ipers on i915g.
Checked that the series d
I picked those draw changes from Jakob's branch. I discarded the first two
commits (regresses glest) and the last one (i915g specific, works around a bug
that was already fixed properly in git). Gives me a ~10% perf improvement in
state-intensive apps like ipers on i915g.
Checked that the series d
