The GE 645 mainframe computer was a development of the GE 635 for use in the Multics project. This was the first computer that implemented a configurable hardware protected memory system. It was designed to satisfy the requirements of Project MAC to develop a platform that would host their proposed next generation time-sharing operating system (Multics) and to meet the requirements of a theorized computer utility.[1] The system was the first truly symmetric multiprocessing machine to use virtual memory, it was also among the first machines to implement what is now known as a translation lookaside buffer,[2] the foundational patent for which was granted to John Couleur and Edward Glaser.[3]
General Electric initially publicly announced the GE 645 at the Fall Joint Computer Conference in November 1965. At a subsequent press conference in December[4] [5] of that year it was announced that they would be working towards "broad commercial availability" of the system. However they would subsequently withdraw it from active marketing at the end of 1966.[6] In total at least 6 sites ran GE 645 systems in the period from 1967 to 1975.[7]
The basic system configuration consisted of a combination of 4 basic modules[8] these were:
The System Controller Modules (SCM) effectively acted as the heart of the system. These were passive devices which was connected to each active device (Processor, GIOC, EMU) and provided the following:[9]
Compared to the rest of the 600 series the 645 did not use the standard IOC's (input/output controllers) for I/O. Nor did it use the DATANET-30 front end processor for communications. Instead both sets of functionality was combined into one unit called a GIOC (Generalized I/O Controller) which provided dedicated channels for both Peripheral (Disc/Tape) and Terminal I/O.[10] The GIOC acted as an Active Device and was directly connected to memory via dedicated links to each System Controller that was present in a specific configuration.
The Extended Memory Unit, though termed a drum, was in reality a large fixed-head hard disk with one head per track,[11] this was a OEM product from Librascope.[12] The EMU consisted of 4,096 tracks providing 4MW (megawords) of storage (equivalent to 16MB). Each track had a dedicated read/write head, these were organised into groups of 16 "track sets" which are used to read/write a sector. A sector is the default unit of data allocation in the EMU and is made up of 80 words, of which 64 words are data and the remaining 16 were used as a guard band. The average transfer rate between the EMU and memory was 470,000 words per second, all transfers were 72-bits (two words) wide, with it taking 6.7μs to transfer 4 words. The unit had a rotational speed of 1,725 rpm, which ensured an average latency of 17.4 milliseconds.
| Component | Small | Typical | Large | |
|---|---|---|---|---|
| System Configuration Console | 1 | 1 | 2 | |
| Processor | 1 | 2 | 4 | |
| GIOC | 1 | 2 | 3 | |
| System ControllersTotal Capacity (Words) | 2128K | 4256K | 81024K | |
| Extended Memory UnitTotal capacity (Words) | 14096K | 14096K | 14096K | |
| Fixed disc (Words) | 33M | 67M | 134M | |
| Magnetic Cards (Words) | -- | 113M | 226M | |
| Magnetic tape handlers | 4 | 16 | 32 | |
| Printers | 2 | 4 | 6 | |
| Card Readers | 1 | 2 | 3 | |
| Card Punches | 1 | 2 | 2 | |
| Perforated Tape | -- | 1 | 2 | |
| Channels for TTY's | 64 | 192 | 384 | |
| Channels for voice-grade communication lines for remote terminals such as such as DATANET-760 / GE-115 | -- | 12 | 18 |
The GE-645 has two modes of Instruction Execution (Master and Slave) inherited from the GE-635, however it also adds another dimension by having two modes of memory addressing (Absolute and Appending). When the process is executing in Absolute Mode addressing is limited to 218 words of memory and any instructions are executed in Master mode. In comparison Append Mode calculates the address using "Appending Words" with an address space of 224 words and with instruction execution occurring in either Master or Slave modes.
By default this is normal mode that the processor should be executing in at any point in time. Nearly all instructions will run in this mode aside from a small set of privileged instructions which cannot execute in this mode. Execution of such instructions will trigger an illegal procedure fault, also the ability to inhibit interrupts (bit 28 of instruction word) is forbidden. Format of instruction addresses is via the Appending Process.
In this mode the processor can execute all instructions and is able to inhibit interrupts while doing so. Like in Slave mode the default form of address formation is via the Appending Process.
All instructions can be executed in this mode and full access is given to any privileged features of the hardware. Interrupts can be inhibited and instruction fetching is limited to a 218 (18-bit) absolute address thus restricting the processor to only been able to access the lower 256 KW of physical core memory. The processor will switch to this mode in the event of a fault or interrupt and will remain in it until it executes transfer instruction whose operand address has been obtained via the appending process.
By default this is normal mode of Memory addressing, both Master and Slave modes normally operate in this mode. Indirect words and operands are accessed via Appending Mechanism via the process of placing a 1 in bit 29 of the executed instruction. Effective addresses are thus either added to a base address, or the offset is linked to the base address.
| Functions | Mode | |||
|---|---|---|---|---|
| Slave | Master | Absolute | ||
| Privileged instructions | No | Yes | Yes | |
| Interrupt inhibit (bit 28 of instruction word) | No | Yes | Yes | |
| Address for Instruction fetch | Appending | Appending | Absolute | |
| Address for Operand fetch | Appending | Appending | Controlled by Bit 29 of instruction word | |
| Restriction of access to other segments or pages | Some | Some (less restrictive than slave) | N/A | |
The 645 processor was divided into four major functional units these were:
One of the key differences from the GE 635 was the addition of "appending unit" (APU) which was used to implement a hybrid "Paged Segmentation" model of virtual memory. The APU was also used to implement a single-level store which is one of the fundamental abstraction that Multics is built around. The instruction format was also extended with the previously unused bit 29 controlling whether the operand address of an instruction used an 18-bit format (bit 29 = 0) or one that was made up of a 3-bit Base Register address with a 15-bit offset (bit 29 = 1).[14] [15]
The instruction format with bit 29 set to 1 is:
1 1 2 2 2 2 3 3
0 2 3 7 8 6 7 8 9 0 5
+---+---------------+---------+-+-+-+------+
|BR | Y | OP |0|I|1| Tag |
+---+---------------+---------+-+-+-+------+
The GE 645 had 8 Address Base Registers (abr's),[16] these could operate in either "paired" or "unpaired" modes.[17] The later Honeywell 6180 changed these to 8 pointer registers. Each abr was 24-bits wide consisting of 18 bits for an address and 6 bits for control functions.[18]
One bit of the control functions field indicates where an abr is "internal" or "external". If an abr is internal, another 3-bit subfield of the control functions field specifies another abr with which this abr is paired; that other abr is external, with the external abr containing a segment number in the address field and the internal abr containing an offset within the segment specified by the external abr. If an instruction or an indirect word refers to an external abr, the address field in the instruction or indirect word is used as an offset in the segment specified by the external abr. If it refers to an internal abr, the address field in the instruction or indirect word is added to the offset in the abr, and the resulting value is used as an offset in the segment specified by the external abr with which the internal abr is paired.
The registers have the following formats depending on how bit 21 is set.
Format as an "external" base, with bit 21 set:
1 1 2 2 22
0 7 8 0 1 23
+------------------+---+-+--+
| PDW |\\\|1|\\|
+------------------+---+-+--+
Format as a component to the effective "internal" address with a pointer to an "external" base, with bit 21 clear:
1 1 2 2 22
0 7 8 0 1 23
+------------------+---+-+--+
| PY |PB |0|\\|
+------------------+---+-+--+
In Multics, an even-numbered abr and the following odd-numbered abr were paired. When writing in Assembly (EPLBSA/ALM)[19] the standard Multics practice was to label these registers as follows:[20]
The naming scheme is based around the following:[21]
The 8 pointer registers in the Honeywell 6180 and its successors served the same purpose as the 4 paired base registers in the GE-645, referring to an offset within a segment.
CTSS had originated in the MIT Computation Center using a IBM 709 and was first demonstrated in November 1961,[22] it was subsequently upgraded to a 7090 in 1962,[23] and finally to a 7094 in 1963.[24] This required modification to these standard systems via the addition of a number of RPQ's which among others added two banks of memory and bank-switching between user and supervisor mode, i.e. programs running in the A-core memory bank had access to instructions that programs running in the B-core bank did not.[25]
Project MAC formally began with signing of contract with ARPA on the 1st of July 1963. By October 1963 they had received a dedicated 7094 to run CTSS under, this was termed the "Red Machine" due to it having red side panels. This would provide a time-sharing environment for Project MAC, and would subsequently be heavily used for the development of Multics. During this period exploratory work was carried out into what a replacement for CTSS would look like and what type of hardware it would require to run on. A committee was formed consisting of Fernando J. Corbató, Ted Glaser, Jack Dennis and Robert Graham with responsibility to visit computer manufacturers to gauge level of interest in the industry to tender for the hardware platform.[26] [27] It was made clear that Project MAC was looking for a development partner given the considerable hardware modifications that would be required to meet their requirements, which were specified as:[28]
They proceeded to visit among others Burroughs, CDC, DEC, General Electric, IBM and Sperry Univac. Of these GE and IBM showed the strongest interest. By the summer of 1964 proposals was received from DEC, IBM and GE, after evaluations by the Technical Committee a unanimous decision was made to accept the GE proposal for the GE 645 which was a design based on the GE 635 but modified to meet the requirements outlined above.
While the GE 645 hardware was being designed and debugged in Phoenix, a system was put in place where a GE 635 could be used to run a simulator known as the 6.36,[30] so that development and checkout of Multics could occur in parallel. This process involved creating a tape on the CTSS system which would be inputted to GECOS on the 635 system in MIT so that it would run under the 6.36 simulator; the resulting output would be carried back via tape to CTSS for debugging/analysis.[31] This simulated environment was replaced by the first 645 hardware in 1967. The GECOS operating system was fully replaced by Multics in 1969 with the Multics supervisor[32] separated by protection rings with "gates" allowing access from user mode.[33]
A later generation in the form of the 645F (F for follow-on) wasn't completed by the time the division was sold to Honeywell, and became known as the Honeywell 6180. The original access control mechanism of the GE/Honeywell 645 were found inadequate for high speed trapping of access instructions and the re-implementation in the 6180 solved those problems.[34] The bulk of these computers running time-sharing on Multics were installed at the NSA and similar governmental sites. Their usage was limited by the extreme security measures and had limited impact on subsequent systems, other than the protection ring.[35]
The hardware protection introduced on this computer and modified on the 6180 was later implemented in the Intel 286 computer processor as a four-layer protection ring, but four rings was found to be too cumbersome to program and too slow to operate. Protection ring architecture is now used only to protect kernel mode from user mode code just as it was in the original use of the 645.