Update Chrome Compositing Docs For Viz OOP-D |
||||
Issue descriptionThe display compositor is being relocated to the GPU process in order to support Vulkan rendering and so a number of major subcomponents were updated to support the new architecture: 1. Software compositing 2. Hit testing 3. Surface synchronization. 4. Display compositor initialization 5. Frame eviction 6. Devtools integration 7. Tab / Window video capture 8. Metrics Instrumentation Docs and slide decks are scattered throughout about these components. We need a single cohesive architecture doc explaining both the motivations and architecture details to neighboring teams and projects that wish to use the compositor.
,
Mar 14 2018
Some initial material to seed this work: Surface sync https://docs.google.com/presentation/d/1vnpF9pC8xEMYI_xMuyIjuStfMAFP-Uw1TMqoHtaeD_8/edit#slide=id.p Tab capture https://docs.google.com/document/d/1dI5irWHGmpp-rJ5w5VtlbI1fWLR2NRvbK8fzo01XuoY/edit OOP-D overview: https://docs.google.com/presentation/d/1SohOTN7hdA2ehzjLYzFbOVIg5gMczuXhroJz_Btpzco/edit#slide=id.p Hit testing https://docs.google.com/presentation/d/1ApNK-Xj1Y_iVl8eeu6ccA_qEJUQYBRb2Sz5ZrNu-TIY/edit
,
Mar 14 2018
,
Mar 14 2018
Impl-side LocalSurfaceId allocation: https://docs.google.com/document/d/1z57NUIBGknBGPvT0vaceQq0Mj775EEVkazoBkF2Ci-M/edit#heading=h.kpiixh4w84ej
,
May 22 2018
,
Nov 15
passing along to kylechar@ if he wishes to continue work here. |
||||
►
Sign in to add a comment |
||||
Comment 1 by fsam...@chromium.org
, Mar 14 2018