Brinch Hansen, P. The nucleus of a multiprogramming system. Comm. ACM 13, 4 (April 1970), 238241, 250.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....mmory. Before themotivation for designing a paging system as cooperating processes can be discussed, these two concepts warrant closer examination. 1.1 Processes The essence of a process is the execution of a program. Numerous definitions of a process are given by various authors IDa68] Ha70] Di68a] but all include the notion of an execution point passing through the instructions of some program. Thus a process is an abstraction of the locus of control that passes through an executing procedure [De66] The address space of a process, that is, the set of all memory addresses the ....

....facilities the operating system provides, such as memory or device management, can themselves be implemented as processes. Two good examples of systems designed around the process concept in this manner are Dijkstra s THE system [Di68b] and a multiprogramming system described by Hansen in [Ha70] In any multi processor computer system, processes offer a straightforward technique for achieving multi processing (the simultaneous execution of two or more programs) Any physical processor (CPU) in the system can execute any user or system process. This permits the operating system to be ....

[Article contains additional citation context not shown here]

Hansen, Per Brinch, "The Nucleus of a Multiprogramming System", Communication .of ,'Cte :A, vol. 13, , 'i (-il, ':1970)i., :pp,.:238-241.

....functionality is provided by components, which implement units of functionaly. Environments serve as the new unifying abstraction: They are containers for stored tuples, components, and other environments, providing a combination of the roles served by file system directories and nested processes [5, 12, 24] in more traditional operating systems. Environments make it possible to group data and functionality when necessary. At the same time, they allow for data and functionality to evolve separately and for applications to store and exchange just data, thus avoiding the two problems associated with ....

P. Brinch Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238--241, 250, Apr. 1970.

....are also an important mechanism for dynamic composition: an environment controls all nested environments and can interpose on their interactions with the kernel and the outside world. Environments thus represent a combination of the roles served by file system directories and nested processes [6, 18, 43] in more traditional operating systems. Figure 2 shows an example environment hierarchy. Access to both local and remote resources is controlled by leases [22] Leases limit the time applications can access resources, such as an environment s tuple storage or a communication channel, and force ....

P. Brinch Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238--241, 250, Apr. 1970.

....group stored data, application components, and hierarchically, other environments. They simplify management of users, their applications, and their data. They can be thought of as a combination of file system directories and nested processes in terms of more traditional operating systems [2, 3, 6]. They group related code and data so that they can be migrated together, for example. These abstractions are crucial to the implementation of the services that will be used by developers of ubiquitous computing applications. They provide an ability to compose applications dynamically. We ....

P. Brinch Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238--241, 250, Apr. 1970.

....we propose is simple: complete elimination of operating system abstractions by lowering the operating system interface to the hardware level. 1 Introduction Throughout the history of computer science there has been a fairly constant opinion that current operating systems are inadequate [4, 7, 9, 11, 15, 18]. The literature is rife with specific examples that describe the cost of the inappropriate, inefficient abstractions peddled by operating systems [2, 4, 12, 13, 18, 23, 24] This situation has persisted for the last three decades, and has survived numerous assaults (object oriented operating ....

Per Brinch Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238--241, April 1970.

....records with named elds, while functionality is provided by components. Environments serve as the new unifying abstraction: They are containers for stored tuples, active components, and other environments, providing a combination of the roles served by le system directories and nested processes [5, 11] in more traditional operating systems. Environments make it possible to group data and functionality when necessary. At the same time, they allow for data and functionality to evolve separately and for applications to store and exchange just data, thus avoiding the two problems associated with ....

P. Brinch Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238-241, 250, Apr. 1970.

.... RFC.net Page 1 of 19 Network Working Group Dave Walden Request for Comments: 61 Bolt Beranek and Newman July 17, 1970 A Note on Interprocess Communication in a Resource Sharing Computer Network The attached note is a draft of a study I am still working on. It may be of general interest to network participants. Walden ....

.... RFC.net Page 1 of 19 Network Working Group Dave Walden Request for Comments: 61 Bolt Beranek and Newman July 17, 1970 A Note on Interprocess Communication in a Resource Sharing Computer Network The attached note is a draft of a study I am still working on. It may be of general interest to network participants. Walden [Page 1] RFC61 RFC.net Page 2 of 19 RFC 61 Interprocess Communication in a Computer Network ....

[Article contains additional citation context not shown here]

P. Hansen, The Nucleus of a Multiprogramming System, CACM, April 1970.

....can make use of the kernel and can in turn be used by the manager. The same basic technique has been used before in other systems to good effect, as discussed by Habermann et al. 6] who refer to it as functional hierarchy. It is also quite similar to the familiar policy mechanism pattern [1, 25]. The main difference is that we place no emphasis on the possibility of using the same kernel with a variety of managers (or without any manager at all) In Pilot, the manager kernel pattern is intended only as a fruitful decomposition tool for the design of integrated mechanisms. 3.1 Layering of ....

Brinch-Hansen, P. The nucleus of a multiprogramming system. Comm. ACM 13, 4 (April 1970), 238--241.

....This dissertation focuses on pages table structures used in conjunction with a software loaded TLB. In particular, this dissertation concentrates on their use in a 64 bit microkernel. The concept of a microkernel (or as originally termed, a nucleus) was first demonstrated on the RC4000 computer [Han70] The following quote describing HYDRA [WCC 74] a later microkernel based system, also describes the basic philosophy of microkernels. at the heart of the system, one should build a collection of facilities of universal applicability and absolute reliability a set of ....

....the choice to optimise the page table for Mungi alone might penalise more conventional operating systems and applications running on the microkernel. Instead, I chose to take a microkernel approach and make no assumptions about the particular strategy needed to optimise a given installation [Han70] The goal of this thesis is to examine, understand, and identify which page table structures minimise the overall cost of the microkernel to applications, and also to examine the limitations of generality: can a single page table design efficiently serve all needs Such an optimised system might ....

Per Brinch Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4), April 1970. BIBLIOGRAPHY 126

....the processor immediately after booting and handle processor exceptions, memory faults, unaligned accesses, TLB misses and all other low level processor features. The Nemesis kernel bears a striking resemblance to the original concept of an operating system kernel or nucleus expressed in [Brinch Hansen70]. The kernel demultiplexes hardware interrupts to the stage where a device specific first level interrupt handler may be invoked. First level interrupt handlers consist of small stubs which may be registered by device drivers. These stubs are entered with all interrupts disabled and with the ....

Per Brinch-Hansen. The Nucleus of a Multiprogramming System. Communications of the ACM, 13(4):238--241,250, April 1970. (p 25)

....location, and open, which moves all contents of an environment into the enclosing environment and deletes the emptied environment. Furthermore, tasks can request to be notified when other environments are moved into or out of their environment. Like nested process structures in other systems [4, 10, 31], the hierarchical nesting of environments provides control. In particular, environments use leases [14] and quotas to limit the resources available to enclosed tasks, tuples, and other environments and to facilitate the e#ective reclamation of these resources. To ensure security, they also ....

P. Brinch Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238--241, 250, Apr. 1970.

....3 integer always refers to the same process; aside from this property the names have no significance. The sending process supplies the data. Any process may send messages (at its expense) to any other process. Messages are received one at a time in the order in which they were sent. See [5] for an actual system very similar to this one, but described from a somewhat different viewpoint. Within this system everything belongs to some process and cannot be accessed by any process other than its owner. Each process is therefore a single domain. It can also be viewed as a separate ....

....process from others. In order to provide useful conventions for sharing among processes, it is necessary to have a systematic way of describing what is to be shared and of controlling access to shared things from various processes. Access to processes can be controlled by a simple tree structure [5, 8], but it can also be handled more generally by the same machinery that we will establish to solve the second problem. It is not at all clear that the scheme described below is the only, or even the best, set of conventions to impose, but it does have the property that almost all the schemes used ....

Hansen, P. B., The nucleus of a multiprogramming system. Comm. ACM 13, 4 (April 1970), p. 238.

....are not evident. Furthermore, we describe some implementation techniques and illustrate why # kernels are inherently not portable, although they improve portability of the whole system. 1 Rationale # kernel based systems have been built long before the term itself was introduced, e.g. by Brinch Hansen #1970# and Wulf et al. #1974#. Traditionally, the word kernel is used to denote the part of the operating system that is mandatory and common to all other software. The basic # GMD SET#RS, 53754 Sankt Augustin, Germany 0 Copyright c # 1995 by the Association for Computing Machinery, Inc. ....

Brinch Hansen, P. 1970. The nucleus of a multiprogramming system. Commun. ACM 13, 4 #April#, 238#241.

....techniques to be useful for some kinds of exokernel extensions, depending on the tradeoffs involved. 4 Related Work Many early operating systems papers discussed the need for extensible kernels [34, 17, 21, 33] Lampson s description of the CAL TSS [20] and Brinch Hansen s microkernel paper [13] are two classic rationales. Hydra was the most ambitious system to have the separation of kernel policy and mechanism as one of its central tenets [34] Modern revisitations of microkernels have also argued for kernel extensibility [16, 26, 1, 28, 30, 10] Anderson [2] and Kiczales et al. 18] ....

Per Brinch Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238--241, April 1970.

....systems but, importantly, the fact that they are unprivileged will enable them to evolve more readily than traditional systems. 1. 1 Relation to other OS structures There is a large literature on extensible operating systems, starting with the classic rationales by Lampson and Brinch Hansen [41, 53, 54]. Previous approaches to extensibility can be coarsely classified in to three groups: better microkernels, virtual machines, and downloading untrusted code into the kernel. We discuss each in turn and then relate exokernels to recent work in extensible operating systems. The exokernel differs from ....

....but there are overlapping lessons (the most painful to rediscover that reasonable defaults must be provided) Both SPIN [9, 32, 71] and Vino [79, 80] are two other extensible operating systems that use downloaded code. Code motion has been a recurrent theme in operating systems since inception [41, 22]. Micro kernels are an attempt to move operating system code out of the harsh environment of the kernel into the more genteel context of processes [41, 53, 2, 77, 84] Virtual machines [20] similarly move operating system code to application level. Interestingly, this is the single feature they ....

[Article contains additional citation context not shown here]

P. Brinch Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238--241, April 1970.

....so that the user can implement application specific policies. Most of the hardware dependencies are limited to a well defined set of modules, to ease the portability of the kernel. The origins of many of the current trends in the modern operating system designs can be traced to the RC4000 [Hansen 1970] nucleus and the Hydra [Levin et al. 1975] design. The RC4000 nucleus design clearly states, as one of its goals, the need to support different operating system implementations above the facilities of the nucleus. Hydra adopted the object model of computing and also elaborated design goals for ....

Per Brinch Hansen. The Nucleus of a Multiprogramming System . Communications of the ACM, pages 238--241, 250, April 1970.

....One of Puma s main goals is to move functionality from the QK into the PCT or into the user libraries whenever possible. The PCT establishes the policies while the QK enforces them. The principle of separating mechanism and policy dates back to Hydra [38] and Per Brinch Hansen s nucleus [16]. The nodes of an MP system running Puma are grouped into service, I O, and compute partitions (Figure 6) The nodes in the service partition run a full featured host OS to enable users to log into the system, perform administrative tasks, and start parallel applications. Nodes which have I O ....

P. B. Hansen. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238--250, Apr. 1970.

....predictable and guaranteed Quality of Service (QoS) for each system resource, rather than optimal peak performance. This is vital when dealing with continuous media (CM) data. The structure of Nemesis and it s I O subsystem have many similarities to operating systems designed over 25 years ago [2, 3, 4, 5]. Aspects of each of these operating systems take on renewed relevance when QoS is the most important consideration. 2 Device Drivers Under Nemesis Nemesis provides QoS guarantees for I O using a non orthodox approach to device abstraction which completely separates the control and data path ....

Per Brinch-Hansen. The Nucleus of a Multiprogramming System. Communications of the ACM, 13(4):238--241,250, April 1970.

....these intrinsics. Concurrent activity is usually represented by processes or threads of control [HR73, Ras86] The term process will be used in the rest of this chapter to denote a separate activity. Information sharing is achieved using either a shared memory mechanism or message passing [Dij65, Bri70]. Understandability is derived from process synchronisation techniques, melding and stability mechanisms [Hoa74, Lor77] A particular model of concurrency can be defined in terms of the specification and interaction of these mechanisms. The model s position on the spectrum of understandability ....

Brinch Hansen, P. "The Nucleus of a Multiprogramming System". CACM 13,4 (1970) pp 238-241.

No context found.

Brinch Hansen, P. The nucleus of a multiprogramming system. Comm. ACM 13, 4 (April 1970), 238241, 250.

No context found.

Brinch Hansen, P. The nucleus of a multiprogramming system. Comm. ACM 13, 4 (April 1970), 238241, 250.

No context found.

P. Brinch Hansen. The nucleus of a multiprogramming system. Comm. ACM, 13(4):238--250, 1970.

No context found.

Hansen, Per Brinch. The nucleus of a multiprogramming system. Communications of the ACM, 13(4):238--250, 1970.

No context found.

P. Brinch Hansen. The nucleus of a multiprogramming system. Comm. ACM, 13(4):238--250, 1970.

No context found.

P. Brinch Hansen. The Nucleus of a Multiprogramming System. CACM 13(4):238-241,250, April, 1970.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC