[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 #11 from Adrienne Walker <enne at google.com>  2012-08-23 10:23:19 PST ---
(In reply to comment #10)
> (In reply to comment #9)
> > (From update of attachment 160056 [details] [details])
> > View in context: https://bugs.webkit.org/attachment.cgi?id=160056&action=review
> > 
> > Although I'm curious what else will go inside the CCPriority.
> 
> In the short term, I plan to store information about "this is a known distance away from the viewport", so I can evict those textures that are >2-3 screens away from the viewport, without evicting the lingering textures first (but not otherwise altering the scoring scheme).

Evicting textures that are 2-3 screens away seems like it could already be done by issuing a smaller texture budget and leaning on the prioritized texture manager to make the decision about which textures should be thrown away or not.

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.

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