Confirmed users
699
edits
Gecko:CrossProcessLayers: Difference between revisions
no edit summary
No edit summary |
|||
| Line 27: | Line 27: | ||
* Build the remoting layers backend | * Build the remoting layers backend | ||
* Publish changes from the content process layer trees and the master process chrome layer tree to shadow trees managed by the GPU thread | * Publish changes from the content process layer trees and the master process chrome layer tree to shadow trees managed by the GPU thread | ||
'''TODO''' stuart/mobile guys/gfx guys. | |||
* Strawman proposal 1: move tile manager into content process, publish canvas tiles as layers. | |||
* Strawman proposal 2: drop tile manager, start from desktop-browser layer manager in content process, add fennec heuristics to that. | |||
= Implementation Details for Fennec = | = Implementation Details for Fennec = | ||
| Line 75: | Line 80: | ||
cjones is in favor of a first implementation where the content process only publishes a single "screen layer". Unsure how video fits into this, although decoding in content process seems fine. Tentatively in favor of initially assuming content process can use GPU so that we can get baseline perf numbers to compare to if we decide to take away GPU access from content. | cjones is in favor of a first implementation where the content process only publishes a single "screen layer". Unsure how video fits into this, although decoding in content process seems fine. Tentatively in favor of initially assuming content process can use GPU so that we can get baseline perf numbers to compare to if we decide to take away GPU access from content. | ||
= Concurrency model for remote layers = | = Concurrency model for remote layers = | ||