Advertisement

PUMA — A Capability-Based Architecture to Support Security and Fault Tolerance

  • Carsten Vogt
Conference paper
Part of the Workshops in Computing book series (WORKSHOPS COMP.)

Abstract

In this paper, we give an overview of the PUMA system, a fault-sensitive, object-based computer architecture. The primary goal in designing PUMA was to build up a system in which hard- and software errors are either avoided beforehand or definitely detected and corrected. Additionally, PUMA is intended to overcome some drawbacks of the von Neumann approach and to provide a basis for the efficient implementation of high-level languages.

We describe PUMA’s object and process concept and sketch the architectural design of the processor. Moreover, the implementation of object-oriented languages and the structure of the storage hierarchy are discussed.

Keywords

Main Memory Machine Instruction Exception Handler Object Descriptor Composite Object 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Colwell, R. P., Gehringer, E. J. and Jensen, E. D. “Performance Aspects of Architectural Complexity in the Intel 432”. ACM Transactions on Computer Systems, 6, 3, August 1988, pp. 297–339CrossRefGoogle Scholar
  2. 2.
    Denning, P. J. “Working sets past and present”. IEEE Transactions on Software Engineering, 6, 1, January 1980, pp. 64–84CrossRefGoogle Scholar
  3. 3.
    Fabry, R. S. “Capability-based Addressing”. CACM, 17, 7, July 1974, pp. 403–411Google Scholar
  4. 4.
    v. d. Heide, K., Kirchner, C., Skupin, U. and Vogt, C. “Die Puffermaschine: Entwurf und Realisierung einer fehlertoleranten, objektorientierten Rechnerarchitektur”. Research Reports Nos. 387/391, Forschungsinstitut für Funk und Mathematik (FFM), D-5307 Wachtberg-Werthhoven, West Germany, December 1988/ May 1989Google Scholar
  5. 5.
    Grünewald, W. “PASCAL für die Puffermaschine”. Research Report No. 397, Forschungsinstitut für Funk und Mathematik (FFM), D-5307 Wachtberg-Werthhoven, West Germany, March 1990Google Scholar
  6. 6.
    Harland, D. M. and Beloff, B. “OBJEKT - A Persistent Object Store With An Integrated Garbage Collector”. ACM SIGPLAN Notices, 22, 4, April 1987, pp. 70–79CrossRefGoogle Scholar
  7. 7.
    v. d. Heide, K. “A General Purpose Pipelined Ring Architecture”. In Proc. CONPAR 86, Lecture Notes in Computer Science, 237, Springer-Verlag, 1986, pp. 198–205Google Scholar
  8. 8.
    Knuth, D. E. “The Art Of Computer Programming, Vol. 1: Fundamental Algorithms”. Addison-Wesley, Reading (Mass. ), 1968zbMATHGoogle Scholar
  9. 9.
    Nett, E., Großpietsch, K., Jungblut, A., Kaiser, J., Kröger, R., Lux, W., Speicher, M. and Winnebeck, H. “PROFEMO - Design and Implementation of a Fault Tolerant Distributed System Architecture”. GMD-Studien Nr. 100, GMD, D-5205 St. Augustin, June 1985Google Scholar
  10. 10.
    Prieve, B. G. and Fabry, R. S. “VMIN - An Optimal Variable Space Page Replacement Algorithm”. CACM, 19, 5, May 1976, pp. 295–297zbMATHGoogle Scholar
  11. 11.
    Stroustrup, B. “What is ‘Object-oriented Programming’?”. In Proc. ECOOP’87, BIGRE + GLOBULE, 54, Rennes, France, June 1987, pp. 57–76Google Scholar
  12. 12.
    Vogt, C. “A new approach to optimal cache scheduling”. Information Processing Letters, 30,6, March 1989, pp. 303–310Google Scholar
  13. 13.
    Vogt, C. “A buffer-based method for storage allocation in an object-oriented system”. IEEE Transactions on Computers, 39, 3, March 1990, pp. 375–383CrossRefMathSciNetGoogle Scholar
  14. 14.
    Wegner, P. “Classification in object-oriented systems”. ACM SIGPLAN Notices, 21, 10, October 1986, pp. 173–182CrossRefMathSciNetGoogle Scholar

Copyright information

© British Computer Society 1990

Authors and Affiliations

  • Carsten Vogt
    • 1
  1. 1.Forschungsinstitut für Funk und Mathematik (FFM)Deutschland

Personalised recommendations