One general question - ShaderDiskCache needs access to the disk, so I imagine it would be outside of Mus, if Mus is sandboxed. I don't think GpuDataManager needs access to the disk, so it could be called inside the sandbox, though it doesn't have to. Do you know if you'd use it directly from Mus, or from whatever launches Mus? Worth thinking about.
Good question! We probably don't want Mus to have direct access to disk. It might access disk through the file service? I'm not sure. Adding a bunch of folks (ben@, sky@, jam@) to discuss.
We're also actively talking about a Mus "Backup process": the thing that reboots Mus if it crashes. I wonder if we can make it the Mus GpuHost process...More things to think about..
I think it would be preferable to have a shader cache mojo service. It seems the kind of component that we would want to position flexibly as mus development proceeds.
Given that we have a separate file system service, doesn't it seem reasonable for the gpu service to obtain (or be given) an appropriately configured mojo pipe by the gpu host that lets it read/write shader data to the file system service?
Comment 1 by fsam...@chromium.org
, Apr 18 2016