Firefly: a multiprocessor workstation

Charles P. Thacker, Lawrence Stewart

1987 · 56 citations · 3 references

DOIFull text

Open access

Concepts

TL;DR

Firefly is a shared‑memory multiprocessor workstation built around 1–7 MicroVAX 78032 CPUs, each with a floating‑point unit and 16 KB coherent cache, supporting 4–16 MB of memory and standard DEC QBus I/O including Ethernet, disks, and a 1024×768 monochrome display, with optional color and high‑capacity disk controller. The paper sets out to describe Firefly’s goals, architecture, implementation, and performance analysis, and to evaluate how effectively SRC’s software supports multiprocessing. Firefly achieves multiprocessing through multiple threads of control in a single address space, uses remote procedure calls for uniform communication, and runs a software layer that emulates the Ultrix system‑call interface. The system successfully emulates the Ultrix system‑call interface, as illustrated by the block diagram in Figure 1.

Abstract

Firefly is a shared-memory multiprocessor workstation that contains from one to seven MicroVAX 78032 processors, each with a floating point unit and a sixteen kilobyte cache. The caches are coherent, so that all processors see a consistent view of main memory. A system may contain from four to sixteen megabytes of storage. Input-output is done via a standard DEC QBus. Input-output devices are an Ethernet controller, fixed disks, and a monochrome 1024 x 768 display with keyboard and mouse. Optional hardware includes a high resolution color display and a controller for high capacity disks. Figure 1 is a system block diagram.The Firefly runs a software system that emulates the Ultrix system call interface. It also supports medium- and coarse-grained multiprocessing through multiple threads of control in a single address space. Communications are implemented uniformly through the use of remote procedure calls.This paper describes the goals, architecture, implementation and performance analysis of the Firefly. It then presents some measurements of hardware performance, and discusses the degree to which SRC has been successful in producing software to take advantage of multiprocessing.

References

3