Sorry, one last thing I would be interested in looking into: fault Tolerance of shared state.
In particular, can a crashing process currently break shared data structures thus breaking the whole browser (e.g. leaving shared data structures in an inconsistent state)? Thanks, Fady On Mon, Jan 4, 2010 at 8:22 PM, Adam Langley <[email protected]> wrote: > On Mon, Jan 4, 2010 at 5:17 PM, Fady Samuel <[email protected]> wrote: > > I am aware there will be synchronization issues. I am a grad student who > has > > been studying concurrent and lock-free data structures for a while now. > I'm > > actually hoping to apply some of my research in Chromium as a proof of > > concept. > > I'm also interested in looking into state that is already shared but > makes > > excessive use of locking and may be hindering performance. Any shared > state > > applying iterators of some kind would be interesting as well for me. > > On Linux (only) the Skia glyph caches are replicated across renderers. > > > AGL > -- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
