native threads

Alan Grimes alangrimes at starpower.net
Mon Apr 11 20:41:53 UTC 2005


I don't know who's been talking in terms of running an interpreter for
EACH Squeak process...

But clearly, the best design is to implement a MANY:FEW scheduler. This
way you still have light-weight squeak processes _AND_ you get to take
advantage of hardware threads.

Additionally, your time critical stuff can be bound to a specific thread
and get (to within the limits of the host OS), exclusivity on a physical
CPU...



More information about the Squeak-dev mailing list