[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 #13 from Christopher Cameron <ccameron at chromium.org>  2012-08-23 14:13:04 PST ---
(In reply to comment #12)
> (In reply to comment #11)

> > Why do you need a separate mechanism for this?  It seem like if you add additional information that can be used to prioritize textures, then the texture manager should be the one using it.
> 
> Is this perhaps in the context of the impl thread doing some management, since that's where GPU memory manager limits arrive via the graphics context on that thread?

That's exactly it.  This is so that the impl thread can evict "some but not all" textures.  The impl thread will need to guess which textures the main thread would have deleted (were the main thread to have made the choice), since it doesn't have direct access to the prioritized texture manager.

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