ACM Home Page
Please provide us with feedback. Feedback
Implementing virtual memory in a vector processor with software restart markers
Full text PdfPdf (404 KB)
Source International Conference on Supercomputing archive
Proceedings of the 20th annual international conference on Supercomputing table of contents
Cairns, Queensland, Australia
SESSION: High performance computing--supercomputing table of contents
Pages: 135 - 144  
Year of Publication: 2006
ISBN:1-59593-282-8
Authors
Mark Hampton  MIT CSAIL, Cambridge, MA
Krste Asanović  MIT CSAIL, Cambridge, MA
Sponsors
SIGARCH: ACM Special Interest Group on Computer Architecture
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 7,   Downloads (12 Months): 43,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1183401.1183422
What is a DOI?

ABSTRACT

Traditional vector architectures often lack virtual memory support because it is difficult to support fast and precise exceptions for these machines. In this paper, we propose a new exception handling model for vector architectures based on software restart markers, which divide the program into idempotent regions of code. Within a region, the processor can commit instruction results to the architectural state in any order. If an exception occurs, the machine jumps immediately to the exception handler and kills ongoing instructions. To restart execution, the operating system has just to begin execution at the start of the region. This approach avoids the area and energy overhead to buffer uncommitted vector unit state that would otherwise be required with a high-performance precise exception mechanism, but still provides a simple exception handling interface for the operating system. Our scheme also removes the requirement of preserving vector register file contents in the event of a context switch. We show that using our approach causes an average performance reduction of less than 3% across a variety of benchmarks compared with a vector machine that does not support virtual memory.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Trimaran homepage. http://www.trimaran.org.
 
2
 
3
D. I. August et al. Sentinel scheduling with recovery blocks. Technical Report CRHC-95-05, Center for Reliable and High-Performance Computing, University of Illinois at Urbana-Champaign, January 1995.
 
4
K. Bala et al. Software prefetching and caching for translation lookaside buffers. In OSDI-1, November 1994.
 
5
D. H. Brown Associates, Inc. Cray launches X1 for extreme supercomputing, November 2002.
 
6
W. Buchholz. The IBM System/370 vector architecture. IBM Systems Journal, 25(1), 1986.
 
7
DEC. Exception reporting mechanism for a vector processor. U.S. Patent 5,043,867, August 1991.
 
8
9
 
10
 
11
 
12
13
14
 
15
 
16
K. Kitagawa et al. A hardware overview of SX-6 and SX-7 supercomputer. NEC Research & Development Journal, 44(1), January 2003.
 
17
A. Klaiber. The technology behind Crusoe processors. White paper, Transmeta Corporation, January 2000.
 
18
19
20
 
21
 
22
23
 
24
25
26
27
 
28
29
 
30
31

Collaborative Colleagues:
Mark Hampton: colleagues
Krste Asanović: colleagues