[Webkit-unassigned] [Bug 94751] [chromium] Use an opaque type for texture priority

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=94751


Eric Penner <epenner at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WONTFIX                     |FIXED




--- Comment #23 from Eric Penner <epenner at chromium.org>  2012-08-23 16:42:02 PST ---
(In reply to comment #22)
> Closing this out, since I'll go about this a different way.  Thanks for the feedback!

Since I already wrote this, here goes:

I think the only case where multi-threading might help impl-side painting would be when we have many paint jobs in queue, and don't want to pre-allocate textures for all those jobs. So we might want a way to do 'acquireTexture()' and steal textures as late as possible on a paint thread (this also requires zero-copy multi-threaded access to write to the textures). I think ideally though most of it should stay on the impl thread. It gets very confusing if, for example, priorities are set or textures are prioritized on other threads, or something like that.

For partially managing textures on impl thread, that's tricky and not sure what the best solution is there... Best I can think of would be to have flags on each texture (eg 'visible') that are pushed to the impl thread, such that we can delete some textures instead of all of them (and then notify similar to what we do now via 'allBackingTexturesWereDeleted').

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.