Confirmed users
699
edits
Gecko:CrossProcessLayers: Difference between revisions
Jump to navigation
Jump to search
→Proposal
| Line 12: | Line 12: | ||
* Since we're pushing changes across threads anyway, we might as well push them across process boundaries at the same time, so push them all the way to the GPU process | * Since we're pushing changes across threads anyway, we might as well push them across process boundaries at the same time, so push them all the way to the GPU process | ||
* Therefore, the GPU process maintains a set of shadow layer trees and is responsible for compositing them | * Therefore, the GPU process maintains a set of shadow layer trees and is responsible for compositing them | ||
* Compositing a shadow layer tree either results in a buffer that's rendered into a window, or a buffer that is later composited into some other layer tree | * Compositing a shadow layer tree either results in a buffer that's rendered into a window, or a buffer that is later composited into some other layer tree | ||
** We can reduce VRAM usage at the expense of increased recomposition work by recompositing a content process layer tree every time we composite its parent layer tree and not having a persistent intermediate buffer | ** We can reduce VRAM usage at the expense of increased recomposition work by recompositing a content process layer tree every time we composite its parent layer tree and not having a persistent intermediate buffer | ||
** We can control the scheduling of content layer tree composition | ** We can control the scheduling of content layer tree composition | ||