[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





--- Comment #20 from Christopher Cameron <ccameron at chromium.org>  2012-08-23 14:53:51 PST ---
(In reply to comment #18)
> (In reply to comment #17)
> > For (2), I'd imagine that impl-side painting would move this off of the main thread (and of course, then, it doesn't have to worry about not knowing what textures the impl thread has destroyed).
> 
> Well, then it will be an update thread instead of main thread, there are the same/similar cross thread issues to deal with though?

The big difficulty is in issue (1), where the priorities can be changed by the main thread.

True, issue (2) still exists, but it is not nearly as hard a problem as (1) -- the amount of state that needs to be shared is fairly simple and localized (the impl thread needs to know "what things are other threads currently painting", and the update thread needs to know "don't grab more work for just a second because a reprioritization is in progress").

This all comes with the caveat that I'm not up to speed on impl-side painting.

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