Path: utzoo!attcan!uunet!world!decwrl!sdd.hp.com!usc!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!a.gp.cs.cmu.edu!koopman
From: koopman@a.gp.cs.cmu.edu (Philip Koopman)
Newsgroups: comp.lang.forth
Subject: Re: Concurrency
Summary: inter- or intra-processor?
Message-ID: <10561@pt.cs.cmu.edu>
Date: 25 Sep 90 14:01:15 GMT
References: <3287@mindlink.UUCP>
Organization: Carnegie-Mellon University, CS/RI
Lines: 17

In article <3287@mindlink.UUCP>, a684@mindlink.UUCP (Nick Janow) writes:
> As far as I can see, the main problem in parallelism is the efficient
> communication of data and instructions between processors.  Stacks are an
> efficient way of passing data between words (tasks, subroutines, whatever);
> perhaps there's some way of passing data and/or instructions between processors
> using stacks.
I guess I'm thinking more about fine-grain parallelism where a single stack
processor can have multiple active instructions (super-scalar).  Stacks
as information transfer mechanisms start getting more into interconnection
than processor design (but, that's an important design consideration too).

> Breakthroughs often come about by
> keeping several previously unrelated ideas in your thoughts while pondering a
> problem.
I agree completely.

-- Phil