The Full Wiki

Capability-based addressing: Wikis


Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.


From Wikipedia, the free encyclopedia

In computer science, capability-based addressing is a scheme used by some computers to control access to memory. Under a capability-based addressing scheme, pointers are replaced by protected objects (called capabilities) that can only be created through the use of privileged instructions which may only be executed by the kernel (or some other privileged process authorised to do so). This effectively allows the kernel to control which processes may access which objects in memory without the need to use separate address spaces and therefore requiring a context switch when an access occurs. This allows an efficient implementation of capability-based security.


Practical implementations

Two techniques are available for implementation:

  • Require capabilities to be stored in a particular area of memory that cannot be written to by the process that will use them. For example, the Plessey System 250 required that all capabilities be stored in capability-list segments.
  • Extend memory with an additional bit, writable only in supervisor mode, that indicates that a particular location is a capability. This is a generalization of the use of tag bits to protect segment descriptors in the Burroughs large systems, and it was used to protect capabilities in the IBM System/38.

While popular in research systems, capability-based addressing is not commonly available in commercial computer systems, with a few exceptions (e.g. Plessey System 250). The most widely sold architecture using capability-based addressing is the IBM System/38 (but users of these systems were rarely aware of its sophisticated memory-addressing model).

The designers of the System/38's descendent systems, AS/400 and iSeries, removed capability-based addressing. The reason given for this decision[1] is that they could find no way to revoke capabilities (although patterns for implementing revocation in capability systems had been published as early as 1974[2], even before the introduction of System/38).

Chronology of systems adopting capability-based addressing

Further potential additions can be found here: [1].


  1. ^ Frank G. Soltis Fortress Rochester: The Inside Story of the IBM ISeries pp.119, 283
  2. ^ Redell, David D. (November 1974). Naming and Protection in Extendible Operating Systems. PhD. Thesis, also published as Project MAC TR-140. MIT.  


  • W. David Sincoskie, David J. Farber: SODS/OS: Distributed Operating System for the IBM Series/1. Operating Systems Review 14(3): 46-54 (July 1980)
  • G. D. Buzzard, T. N. Mudge (1983) [OBJECT-BASED COMPUTER SYSTEMS AND THE ADA PROGRAMMING LANGUAGE ] [3] . THE UNIVERSITY OF MICHIGAN - Computer Research Laboratory and Robotics Research Laboratory Department of Electrical and Computer Engineering

External links



Got something to say? Make a comment.
Your name
Your email address