The transputer is a programmable VLSI component with communication links for point-to-point connection to other transputers. Occam (*) is a language that enables a multi-transputer system to be described as a collection of processes that ogerate concurrently and communicate using message passing via named channels. The INMOS transputer architecture is standardized at the level off the definition of occam (rather than at the level of the definition of an instruction set). The implementation of the first commercially available transputers is illustrated by describing the implementation of occam. The paper concludes with outline examples of some applications. 1 Introduction The transp~ater architecture has been developed to fulfil four main objectives: To create a commercial product range that sets new standards in ease of programming and ease of engineering. To provide the maximum performance to the user. To exploit future developments in VLSI technology within a compatible family. To create a programmable component that can be used to build systems with large numbers of concurrent computing elements. VLSI currently permits 5-10 MIP processors to be manufactured in volume for low prices. There is therefore no economic barrier to the construction of very powerful computer systems containing many processing elements, The challenge is a technical one: how to engineer a system with, say, 1000 processors so as to make the inherent concurrency usable, and how to support the design of applications to take advantage of this amount of concurrency. (*) oceam is a trade mark of the INMOS Group of Companies In the transputer architecture, the exploitation of a high degree of concurrency is made possible through a decentralized model of computation, in which local computation takes place on local data, and concurrent processes communicate by passing messages on point to point channels. The localized communications architecture also has substantial engineering advantages, described below. An important design objective of oecam and the transputer was to provide the same concurrent programming techniques both for a single transputer and for a network of transputers. Consequently, the features of occam were chosen to ensure an efficient distributed implementation on transputer systems. The concurrent processing mechanisms within the transputer were then designed to match. The result is that a program ultimately intended for a network of transputers can be compiled and executed efficiently by a single computer used for program development. Once the logical behaviour of the program has been verified, the program may be configured for …
[1]
Jon M. Kerridge,et al.
Three solutions for a robot arm controller using Pascal‐Plus, occam and edison
,
1984,
Softw. Pract. Exp..
[2]
A. W. Roscoe.
Denotational Semantics for occam
,
1984,
Seminar on Concurrency.
[3]
B. J. Curry.
Language-based architecture eases system design. III. (Occam)
,
1984
.
[4]
Don Fay,et al.
Working with occam: a program for generating display images
,
1984,
Microprocess. Microsystems.
[5]
George Radin.
The 801 Minicomputer
,
1983,
IBM J. Res. Dev..
[6]
C. A. R. Hoare,et al.
Programs as Executable Predicates
,
1984,
FGCS.
[7]
Norman P. Jouppi,et al.
The MIPS Machine
,
1982,
COMPCON.
[8]
ScienceDirect.
Microprocessors and microsystems
,
1978
.
[9]
David A. Patterson,et al.
Architecture of a VLSI instruction cache for a RISC
,
1983,
ISCA '83.
[10]
Robert P. Colwell,et al.
Peering through the RISC/CISC fog: an outline of research
,
1983,
CARN.
[11]
R. J. Joenk,et al.
IBM journal of research and development: information for authors
,
1978
.
[12]
J. G. McWhirter,et al.
A practical comparison of the systolic and wavefront array processing architectures
,
1985,
ICASSP '85. IEEE International Conference on Acoustics, Speech, and Signal Processing.
[13]
David A. Patterson.
RISC watch
,
1984,
CARN.