Thanks for the reply. Actually, have already checked the mentioned docs. Doesn't give high level idea about threads (named, unnamed) and thread level communication.
Certainly named threads are easy to track but unamed aren't. Anyways, I just tapped into thread creation functions and tracked creation details about unnamed and named threads :) Any sugestion for meaningful tapping into thread communication? BR/ Lalit Lalit Arora <[email protected]> writes: > Hi, > > I am trying to understand b2g process and container process internals. > > After booting to homescreen, on executing "b2g-ps.sh -t" (ref: > http://github.com/mozilla-b2g/gonk-misc/blob/master/b2g-ps), script is > listing threads in action for all b2g spawned process (b2g, usage, > homescreen). Some of the threads (b2g, dom worker, binder) have same naming > which is adding to confusion. > > Any reference document (or source reference) regarding b2g, container > process internals (especially explains/allows to understand threads > role/responsibility) and their association with each other, gonk/external > component)? https://wiki.mozilla.org/Electrolysis https://developer.mozilla.org/en-US/docs/Multi-Process_Architecture The documentation is scattered around and may not reflect the current b2g architecture. In short, there are two process types currently, the chrome process (b2g process) and the content process (plugin-container process). On b2g these two processes share many properties. They both have a main thread, many worker threads and binder threads, and they both could render web pages. Some high privileged actions are restricted to the b2g process, so the content process needs to delegate the action to the b2g process. Other threads, I think it's easy to guess what they do from their names. Kanru _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
