Dan Sugalski <[EMAIL PROTECTED]> wrote: >=item Interpreter pools will share allocation pools
> All the interpreters in an interpreter pool will share header and > memory allocation pools. What about temporary PMCs (or strings)? Evaluating a non-trivial expression can have lot of these. Each new temp would need a lock on the memory sub-system. Combined with the cost of: >=item All shared PMCs must have a threadsafe vtable > The first thing that any vtable function of a shared PMC must do is to > aquire the mutex of the PMCs in its parameter list i.e. typically 3 mutexes, it could be that the vtable of a shared PMC should just grab one interpreter lock (of the owner of that PMC) and that not all is shared (especially not the temps). leo
