Proceedings of the Twenty-Seventh Hawaii International Conference on System Sciences HICSS-94 1994
DOI: 10.1109/hicss.1994.323149
|View full text |Cite
|
Sign up to set email alerts
|

The S3.mp scalable shared memory multiprocessor

Abstract: S3.mp (Sun's Scalable Shared memory MultiProcessor)is a research project to demonstrate a low overhead, high throughput communication system that is based on cache coherent distributed shared memory (DSM). S3.mp uses distributed directories and point-to-point messages that are sent over a packet switched interconnect fabric to achieve scalability over a wide range of configurations. S3.mp uses a new CMOS serial link technology that achieves transmission rates >lGbitlsec and that is directly integrated into a p… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
52
0

Year Published

1994
1994
2008
2008

Publication Types

Select...
5
3
2

Relationship

0
10

Authors

Journals

citations
Cited by 54 publications
(52 citation statements)
references
References 6 publications
0
52
0
Order By: Relevance
“…Such controllers appear in the MIT Alewife machine [1], the KSR1 machine [15], the Stanford DASH multiprocessor [17], and the SGI Origin 2000 [16]. As o increases, the controller becomes less hardwired and more general-purpose, from specialized coprocessors like those in the Stanford FLASH multiprocessor [14] and the Sun S3.mp [22], through inexpensive off-the-shelf processors on the memory bus as in Typhoon-1 [23], to a controller on the I/O bus of the main processor like those in SHRIMP [3], and the IBM SP2 [28]. We also vary the node-to-network bandwidth from 400 MB/s (g 1 ) down to 25 MB/s (g 16 ), to analyze the effect of reducing network bandwidth on the applications under consideration.…”
Section: Design Spacementioning
confidence: 99%
“…Such controllers appear in the MIT Alewife machine [1], the KSR1 machine [15], the Stanford DASH multiprocessor [17], and the SGI Origin 2000 [16]. As o increases, the controller becomes less hardwired and more general-purpose, from specialized coprocessors like those in the Stanford FLASH multiprocessor [14] and the Sun S3.mp [22], through inexpensive off-the-shelf processors on the memory bus as in Typhoon-1 [23], to a controller on the I/O bus of the main processor like those in SHRIMP [3], and the IBM SP2 [28]. We also vary the node-to-network bandwidth from 400 MB/s (g 1 ) down to 25 MB/s (g 16 ), to analyze the effect of reducing network bandwidth on the applications under consideration.…”
Section: Design Spacementioning
confidence: 99%
“…To minimize changes to the memory system, TokenTM stores 16 metabits per 64-byte memory block using recoded error-correction codes, as pioneered by S3.mp [21]. Standard DRAM modules uses 72-bit codewords to protect 64 data bits with single error correction and double error detection (SECDED).…”
Section: Metastate At Memorymentioning
confidence: 99%
“…Such flexible protocol processors, used in the Piranha system [1], STiNG multiprocessor [19], S3.mp [23], etc., allow late binding of the protocol, flexibility in the choice of protocol, and a relatively easy and fast protocol verification phase. Coherence messages arrive at the processor interface (PI inbound) or the network interface (NI inbound) and wait for the dispatch unit to schedule them.…”
Section: Node Controller Architecturementioning
confidence: 99%