2008/7/7 Andreas Raab <andreas.raab at gmx.de>:
> Peter William Lount wrote:
>>
>> Why prevent others from having their needed multiple native threads?
>>
>
> It's not about preventing anything. If you have a proposal for how to do
> multiple threads per image I will most definitely listen, and if it is a
> reasonable proposal (i.e., one that can be implemented with bounded
> resources) I will even try to find funding for it. However, until such a
> time that there is a proposal I will drop this pointless discussion since,
> simply put, there is nothing to discuss here. The only available path at
> this point is by using one native thread per image and consequently that's
> what's going to happen.
>

I have some ideas of using Island/Vat model in future CorruptVM project.

I'm not going into deep detail right now, but the essence of model is following:

- an Island is the group of objects sharing same memory region.
Objects in island can communicate without need in synchronization.
- a Process is the state of computation running in some island.
Islands can have many processes, but only one of them can be active at
single point of time.
- a native thread treated by system as system resource, and scheduler
doing its job to distribute the available resources among islands.

> Cheers,
>  - Andreas
>
>



-- 
Best regards,
Igor Stasenko AKA sig.