gpu: Unify in process ContextProviders |
|||||||||
Issue descriptionWe would like to get rid of CommandBufferLocal which lacks test and production coverage currently. It also has its own scheduling which doesn't match the rest of Chrome. Along the lines of "Unify all things!", I think it makes sense to work towards unifying all inprocess context providers. Dana identified the following in processs ContextProviders: 1. AwRenderThreadContextProvider 2. BlimpContextProvider 3. InProcessContextProvider 4. CommandBufferLocal (that mus uses). This bug tracks progress towards unification.
,
May 11 2016
,
May 11 2016
It looks like there are two InProcessContextProviders (not including Vulkan of course): cc/test and ui/compositor/test too. It seems like moving all these to somewhere in gpu might make sense.
,
May 11 2016
Sorry, I just realized that should've said SurfacesContextProvider which has a CommandBufferLocal. If we get rid of SurfacesContextProvider, then we get rid of CommandBufferLocal.
,
May 18 2016
,
Jun 24 2016
,
Oct 4 2016
,
Nov 27 2016
Assigning to myself to investigate further soon. Now that Mus uses InProcessContextProvider, we've actually made some progress on this bug. AwRenderThreadContextProvider and BlimpContextProvider also use InProcessCommandBuffer, IIRC, so maybe there's an opportunity for more unification here.
,
Nov 28 2016
AwRenderThreadContextProvider is special in that it uses a pre-made GLSurface I think, but this shouldn't make things much more difficult.
,
Feb 26 2018
,
Feb 26 2018
,
Aug 13
Blimp is gone. OOP-D uses inProcessContextProvider. CommandBufferLocal is gone. I'm marking as WontFix. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by fsam...@chromium.org
, May 11 2016Components: MUS Internals>GPU