Multy-core CPUs

Sebastian Sastre ssastre at seaswork.com
Thu Oct 18 00:51:04 UTC 2007


Mmmm original, yeah thats a very different approach. Hard to say which one
is best. But for your comments, maybe the primitives way is a path *better*
for the human beigns that program the system in terms of easing that pain. 
 
    Question: that would be a path that prioritizes usability at samlltalk
developer level? if so, for me is more interesting even if it is less
efficient than the other in terms of a couple of more or less [whatever
measure unit] per second that in one year will be duplicated with a cpu with
2 more cores for a few u$s.
 
    Not prioritizing usability and intelectual ergonomy is equal to not
geting the point of all this smalltalk thing, perhaps even more.. all TI
thing. Just a thought.
 
    I'm quite sure that multicore this is the begining of a new crisis for
the industry. But is a good one!
 
    cheers,
 
Sebastian Sastre


  _____  

De: squeak-dev-bounces at lists.squeakfoundation.org
[mailto:squeak-dev-bounces at lists.squeakfoundation.org] En nombre de Steve
Wart
Enviado el: Miércoles, 17 de Octubre de 2007 17:26
Para: The general-purpose Squeak developers list
Asunto: Re: Multy-core CPUs


I don't know if mapping Smalltalk processes to native threads is the way to
go, given the pain I've seen in the Java and C# space.

What might be interesting is to develop low-level primitives (along the
lines of the famed map/reduce operations) that provide parallel processing
versions of commonly used collection functions. 

No idea how easy this would be to do, but on the surface seems more
promising than trying to do process/thread jiggery pokery.

Steve


On 10/17/07, Sebastian Sastre <ssastre at seaswork.com> wrote: 

This is not my area but I imagine that somehow Squeak processes should map
to OS native threads paralellizable by each of the cores. Any chance to
Exupery be of some help on that? I ask because if it is then is a must for 
that future.

        regards,

Sebastian Sastre


> -----Mensaje original-----
> De: squeak-dev-bounces at lists.squeakfoundation.org
<mailto:squeak-dev-bounces at lists.squeakfoundation.org> 
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org] En
> nombre de gruntfuttuck
> Enviado el: Miércoles, 17 de Octubre de 2007 06:10 
> Para: squeak-dev at lists.squeakfoundation.org
> Asunto: Multy-core CPUs
>
>
> How is squeak going to handle multy-core CPUs, if at all? If 
> we see cores of 100 plus in the future and squeak stay as it
> is, I would imagine other languages such as erlang, will look
> more attractive.
> --
> View this message in context:
> http://www.nabble.com/Multy-core-CPUs-tf4639074.html#a13249733
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>
>





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20071017/ed171c66/attachment.htm


More information about the Squeak-dev mailing list