On Aug 28, 7:46 pm, "L. David Baron" <[EMAIL PROTECTED]> wrote: > Jason Orendorff wrote: > > * Add thread-safety to MMgc using the Spidermonkey request model. > > We currently don't pay the cost of thread-safety for most XPCOM objects, > since most objects are main-thread-only. Would doing this impose > significant performance penalties for locking or atomic operations? Or > would most operations still be cheap?
The request model helps prevent two kinds of thread-unsafety: 1) GC colliding with other threads doing stuff 2) two threads touching an object at the same time We only need it for item 1, which is cheap. Individual classes may opt in for item 2. JSObject does. But most XPCOM classes won't-- and so they will incur no cost. Those following along at home can read up on the request model here: SpiderMonkey Internals: Thread Safety http://tinyurl.com/yt5rtr -j _______________________________________________ dev-tech-xpcom mailing list dev-tech-xpcom@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-xpcom
