John Rosenberg and J. L. Keedy. Object management and addressing in the MONADS architecture. In IWPOS87 [IWPOS871987].  Home/Search   Document Not in Database   Summary   Related Articles   Check

....password capabilities results in three benefits. First, we can use conventional microprocessors as our node processors, unlike other proposals to support large address spaces [9, 13] Second, the alternative approach to prevent forgeries of capabilities by segregating them into a separate space [24, 31] prevents users from storing GVAs in their own data structures. Finally passwords effectively increase the sparseness of the address space and allow addresses to be reused. 7 Current Status The page migration and replication system is currently being designed, and a prototype will shortly be ....

J. Rosenberg and J. Keedy. Object management and addressing in the MONADS architecture. In Int. W. Persistent Obj. Syst., Appin, Scotland, 1987.

....when a segment is created or when it is first used. Once the mapping from segments to virtual addresses has been formed, a paging mechanism similar to that of the Atlas computer may be employed. Examples of segmentation systems that utilise this technique are IBM system 38[ibm78b] and Monads[ros87]. These systems only record virtual address mappings for those pages that are present in main memory. To reduce the total cost of implementing these systems the mappings are held in hash tables that are accessed by microprogram. The ideal solution, that of constructing special purpose hardware as ....

Rosenberg J. & Keedy J.L. Object Management and Addressing in the Monads Architecture. Proc. Workshop on Persistent Object Systems: Their Design Implementation and Use, Universities of Glasgow and St.Andrews, PPRR-44, Scotland, 1987, pp114-133.

....in software [Cock84,Care86,Brow89] The activity of the object manager, however, is much more closely related to the memory management functions like paging and virtual memory. A hardware address translation mechanism for persistent objects might improve the performance of persistent systems [Rose85,Rose87]. 1.3 Combining Persistence with Lazy Functional Programming By combining persistence with lazy functional programming, it becomes possible to reuse values which have been computed by a previous program invocation or even by a different program. A combined system has advantages with efficiency and ....

Rosenberg, J. and Keedy, J.L., Object Management and Addressing in the MONADS Architecture, Proceedings of the International Workshop on Persistent Object Systems, Appin, Scotland, 1987

....addresses. The system is (almost) purely a software approach, as it will run on standard hardware, possibly augmented by some add on components to enhance efficiency. The advantage of combining persistence with a single address space was recognised a number of years ago by the MONADS group [6, 7]. MONADS features a special architecture designed to support a large address space. Virtual memory in MONADS is structured to provide hardware support for modularisation and data encapsulation. Sharing is supported by making all modules globally visible, and system protected capabilities are used ....

J. Rosenberg and J. L. Keedy. Object management and addressing in the MONADS architecture. In International Workshop on Persistent Object Systems, volume 2, Appin, Scotland, 1987. IEEE.

....programming languages Elle [Alb 80] and PSAlgol [Atk 82] already handled persistent and transient data uniformly. To date, partial data persistence (without dealing with faults) is part of the the Comandos [Cah 93] project. Data and process persistence including faults is also supported in Monads [Ros 87] and by the KeyKOS [Har 85] nano kernel, first released in 1983. The Eumel L3 concepts and experiences have also influenced the BirliX [Har 92] operating system design at GMD. 3 Principles 3.1 Everything is persistent We did not find any conceptual reason for anything not to be persistent. ....

J.L Rosenberg and J.L. Keedy. Object Management and Addressing in the MONADS Architecture. Proceedings 2nd International Workshop on Persistent Object Systems, Appin 1987, available as PRRR--44, Universities of Glasgow and St. Andrews.

....space is much more fragmented. The simulations also indicate that under a no reuse policy the page tables will continue to grow even when the total amount of allocated memory is not increasing. Our design allows addresses to be reused safely, unlike other approachs which rely on unique addresses [32]. Each time a portion of the address space is reallocated, new passwords are assigned to protect the region (as described in Section 4) invalidating any dangling references. 2.3 Page Location Each allocated page has a unique owner, which is the node holding the master copy of the page. There may ....

J. Rosenberg and J. L. Keedy. Object management and addressing in the MONADS architecture. In Proceedings of the 2nd International Workshop on Persistent Object Systems, Appin, Scotland, 1987. IEEE.

....implemented using logging [11] or some shadowing technique [26] If persistent systems are to be anything other than research vehicles, they must be both stable and resilient. The persistent systems which exhibit these properties and that have been constructed to date, with a few exceptions [19, 33], have been constructed on top of traditional operating systems. Existing operating systems do not provide an ideal platform for the development of persistent systems. This is not surprising since this was never part of their design goals. Indeed, most operating systems have files as their only ....

Rosenberg, J. and Keedy, J. L. "Object Management and Addressing in the MONADS Architecture", Proceedings of the International Workshop on Persistent Object Systems, Appin, Scotland, 1987.

....systems, the stores contain all data including procedures, graphics objects, processes and their associated state. Perhaps the most important feature of persistent systems is that this store is both resilient and stable. Persistent systems that have been constructed to date, with a few exceptions [23, 53], have been constructed on top of traditional operating systems and conventional architectures. In addition these systems have concentrated mainly on language issues and it is only recently that there has been more interest in providing support at a lower level. It is common to find a notion of ....

....section of a segment. This instruction enforces certain rules which limit the propagation of segment capabilities in the system. These rules simplify the problem of garbage collection and allow most segment capabilities to be maintained in an abbreviated form. The rules are described elsewhere [53]. The root of all addressing is defined by a special segment, of which there is one per process, called the base table. An additional machine instruction is provided to load a capability register to point at the base table. By changing the contents of the base table the current addressing ....

[Article contains additional citation context not shown here]

Rosenberg, J. and Keedy, J. L. "Object Management and Addressing in the MONADS Architecture", Proceedings of the International Workshop on Persistent Object Systems, Appin, Scotland, 1987.

No context found.

John Rosenberg and J. L. Keedy. Object management and addressing in the MONADS architecture. In IWPOS87 [IWPOS871987].

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