T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In OOPSLA '86 Conf. Proc., pages 87--106, Portland, OR, Sept. -- Oct. 1986.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... citeshareholder, Globus [15] and WebOS [34] use URL like names for distributed objects or les. Interface description languages date from Xerox Courier [37] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [17] LOOM [18], and the more recent pickling (serialization) of Java [29] Smart RPC [19] is an extension to conventional RPC that allows argument passing using callby reference rather than deep copy call by value. Smart RPC lacks a shared global name space, 25 however, with a well dened cache coherence ....

T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In OOPSLA '86 Conf. Proc., pages 87--106, Portland, OR, Sept. -- Oct. 1986.

....and recursive types were not supported, all shared data had to be accessed indirectly through a local mapping table, and only a single memory model (similar to processor consistency) was supported. Precedents for the automatic management of pointers include Herlihy s thesis work [19] LOOM [24], and the more recent pickling (serialization) of Java [32] Several software only S DSM systems have proposed that programmers explicitly identify the data to be modified in a critical section, either directly [23, 20] or by explicit [36, 4] or implicit [22] association with a ....

T. Kaehler. Virtual Memory on a Narrow Machine for an ObjectOriented Language. In OOPSLA '86 Conf. Proc., pages 87--106, Portland, OR, Sept. -- Oct. 1986.

....process like objects. Quicktalk: A compilable dialect of Smalltalk, from Tektronix. Ball86] Simula: A simulation language with object classes. Birt73] Smalltalk: Programming language and environment from Xerox PARC. Some references detail experinces with implementation details. [Atki86 BYTE81 Born82a Born82b Caud86 Deco86 Deut84 Gold80b Gold83 Gold84 John86 Kaeh86 Kras83 Pasc86 Tesl81 Vegd86] Smallworld: Smalltalk descendent from IBM Yorktown. La#85] Spool: A Prolog based object oriented language from IBM Japan. Fuku86] Squeak: An object oriented language for communicating with mice. Card85a] Strobe: A language providing object oriented support for Lisp. See also Impulse 86. ....

T. Kaehler, "Virtual Memory on a Narrow Machine for an Object-Oriented Language ", ACM SIGPLAN Notices, vol. 21, no. 11, pp. 87-106, Nov 1986.

.... citeshareholder, Globus [15] and WebOS [34] use URL like names for distributed objects or files. Interface description languages date from Xerox Courier [37] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [17] LOOM [18], and the more recent pickling (serialization) of Java [29] Smart RPC [19] is an extension to conventional RPC that allows argument passing using callby reference rather than deep copy call by value. Smart RPC lacks a shared global name space, 25 however, with a well defined cache coherence ....

T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In OOPSLA '86 Conf. Proc., pages 87--106, Portland, OR, Sept. -- Oct. 1986.

....to a unique indexed variable. Objects may contain both kinds of instance variables. 1 Smalltalk 76 supported object virtual memory. An object virtual memory management system called LOOM (Large Object Oriented Memory) has been developed for Smalltalk 80 but has not been made generally available [Kaehler 86a] Implementations of Smalltalk 80 that reside on top of other operating systems implicitly use the paging system of that operating system. 36 temporary variables These variables are analogous to local procedure variables. They exist only during a particular context (activation) and include ....

Ted Kaehler. Virtual Memory on a Narrow Machine for an ObjectOriented Language. In Proceedings of the ACM Conference on ObjectOriented Programming Systems, Languages, and Applications, Portland, Oregon, October

....Various Linda systems [31, 36] also provide a non object oriented distributed shared store. Interface description languages date from Xerox Courier [47] and related systems of the early 1980s. Precedents for the automatic management of pointersinclude Herlihy s thesis work [18] LOOM [22], and the more recent pickling (serialization) of Java [33] Friedman [15] and Agrawal et al. 1] have shown how to combine certain pairs of consistency models in a non version based system. Alonso et al. 2] present a general system for relaxed, user controlled coherence. Yu et al. 48] describe ....

T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In OOPSLA'86 Conf. Proc.,pages 87--106, Portland, OR, Sept. -- Oct. 1986.

....Various Linda systems [32, 37] also provide a nonobject oriented distributed shared store. Interface description languages date from Xerox Courier [47] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [19] LOOM [24], and the more recent pickling (serialization) of Java [34] Friedman [15] and Agrawal et al. 2] have shown how to combine certain pairs of consistency models in a non version based system. Alonso et al. 3] present a general system for relaxed, user controlled coherency. We explore a real ....

T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In OOPSLA '86 Conf. Proc., pages 87--106, Portland, OR, Sept. -- Oct. 1986.

....data structures. Similar facilities can be found in DCOM, in Emerald [5] and in the more recent pickling (serialization) of Java [9] Wilson s page fault based pointer swizzling [14] dates from 1991. Similar mechanisms can be found in dynamic (lazy) linkers [3] and in Lisp systems (e.g. LOOM [6]) for limited address space machines. Several other groups have recently begun to explore the notion of shared state for processes spread across the Internet. References to many of these can be found in our to appear paper at LCR 2000 [2] 5 Status and Future Work As of April 2000, we have ....

T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In OOPSLA '86 CONF PROC, pages 87--106, Portland, OR, SEP -- OCT 1986.

....Various Linda systems [37, 32] also provide a nonobject oriented distributed shared store. Interface description languages date from Xerox Courier [46] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [19] LOOM [24], and the more recent pickling (serialization) of Java [34] Friedman [15] and Agrawal et al. 2] have shown how to combine certain pairs of consistency models in a non version based system. Alonso et al. 3] present a general system for relaxed, user controlled coherency. We explore a real ....

T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In OOPSLA '86 CONF PROC, pages 87--106, Portland, OR, SEP -- OCT 1986.

....data structures. Similar facilities can be found in DCOM, in Emerald [4] and in the more recent pickling (serialization) of Java [8] Wilson s page fault based pointer swizzling [13] dates from 1991. Similar mechanisms can be found in dynamic (lazy) linkers [2] and in Lisp systems (e.g. LOOM [5]) for limited address space machines. Several other groups have recently begun to explore the notion of shared state for processes spread across the Internet. References to many of these can be found in our LCR 2000 submission [1] 5 Status and Future Work As of March 2000, we have implemented ....

T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In OOPSLA '86 Conf. Proc., pages 87--106, Portland, OR, Sept. -- Oct. 1986.

....management. Various Linda systems [32, 29] also provide a non objectoriented distributed shared store. Interface description languages date from Xerox Courier [40] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [16] LOOM [21], and the more recent pickling (serialization) of Java [30] Friedman [12] and Agrawal et al. 2] have shown how to combine certain pairs of consistency models in a non version based system. Alonso et al. 3] present a general system for relaxed, user controlled coherency. We explore a real ....

T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In OOPSLA '86 Conf. Proc., pages 87--106, Portland, OR, Sept.--Oct. 1986.

.... 39, 48, 66, 65, 18, 17] 3 Related work The notion of orthogonal persistence has a long history [7] traced through the development of prototype orthogonal persistent programming languages such as PS Algol [5, 8, 6] and Napier88 [61, 28] and extensions to existing languages such as Smalltalk [55, 54, 77, 44, 40, 38] and Java [10, 52, 9, 53] It is important to note that all of these prototypes rely on support for persistence from an underlying virtual machine, implemented as an interpreter of abstract machine instructions. While dynamic translation (i.e. JIT compilation) can improve performance in these ....

KAEHLER, T. Virtual memory on a narrow machine for an object-oriented language. In Proceedings of the ACM Conference on Object-Oriented Programming Systems, Languages, and Applications (Portland, Oregon, Sept.). ACM SIGPLAN Notices 21, 11 (Nov. 1986), pp. 87--106.

....Execution in a non object oriented procedural language proceeds through the invocation of statically determined procedures. Ignoring possibilities for optimization of residency checks based on local global data flow analysis, every dereference requires a residency check. 1 [ACC82, BC86, KK83, Kae86, CM84, RMS88, SMR89, BBB 88, Ric89, RC90, Ric90, SCD90, WD92, HMB90, Hos91, HM93a, LLOW91, SKW92, WK92] Static OO: Object oriented programs execute through the invocation of methods on objects. A method typically accesses the encapsulated state of its target object. Thus, applying the ....

Ted Kaehler. Virtual memory on a narrow machine for an object-oriented language. In Proceedings of the ACM Conference on Object-Oriented Programming Systems, Languages, and Applications, pages 87--106, Portland, Oregon, September 1986.

....contents Recognition of faulty objects based on reference contents implies that references to faulty objects differ in some way from the ones to non faulty objects. Let us sen how references contents can be tested. Distinguishing through an explicit test A common solution, adopted in E, LOOM [Kaehler 86] and Emerald, is to use global references for faulty objects and local ones for mapped objects. The first use of a global reference forces the mapping of the object and its conversion to the local format (see figure 4.2) Remaining global references to the object are converted when used (see ....

Ted Kaehler. Virtual memory on a narrow machine for an object-oriented language. In Proceedings of OOPSLA 86, Portland, Oregon, September 1986.

....primitives which will be the building blocks of access plans. We call this low level object manipulation interface the Object Manager (OM) interface. Object managers have received attention lately in the context of distributed systems [BHJL86, DLA88, MG89, VKC86] programming environments [Dec86, Kae86, VBD89] and databases [CDRS86, CM84, EE87, HZ87, Kim88] These object managers differ in terms of their support for data abstraction, concurrency and object distribution. In addition, they are typically oriented towards one at a time object access which is an inefficient paradigm for query ....

....via subclassing and inheritance. Smalltalk s significance lies in its uniform, understandable approach and early existence. Detracting from its acceptance are its performance and closed, single user environment. Various schemes such as type checking [Joh86] and improved object management [Kae86, Sta84] have been proposed to improve performance. A distributed version [Dec86] provides multi user capability but does not improve the interface to other programming environments. A.2 POSTGRES POSTGRES [RS87, SR86, Sto86] is a successor to the INGRES [Sto76] relational database system which ....

T. Kaehler. Virtual Memory on a Narrow Machine for an Object-Oriented Language. In Proc. of the Object-Oriented Programming Systems and Languages Conference, pages 87--106, September 1986.

....interchanged. Copying collection compacts allocated memory as a side effect. The basic copying approach suffers from the same problem as mark scan of requiring application processing to stop while the garbage collector is 2 This is similar to the maturing of objects done in the Smalltak LOOM [Kaehl86]. Although the LOOM does not support persistence with fault tolerance it does provide a large non volatile memory. 3 Independent objects are called packets and dependent objects are called datatype values in Avance. A.Bjornerstedt 6 runing. Refinements of the copying approach have been ....

T. Kaehler, "Virtual Memory on a Narrow Machine for an Object-Oriented Language, " Object-Oriented Programming Systems, Languages and Applications, pp. 87106, Portland, Oregon, Sept. 1986.

....narrow client addresses. The following section considers narrow addresses in secondary storage. 5.1 Loom Accessing a large space of objects from a machine with a narrower address space has certainly been done before. One well known system, Loom, is described in [Kaehler and Krasner, 1983] and [Kaehler, 1986]. Loom stands for large object oriented memory , and it provided access from a 16 bit wide machine to objects residing in a 32 bit addressed store on disk. The only goal of that system was to expand the effective virtual memory; we have additional goals. Further, Loom was invented to get around ....

Ted Kaehler. Virtual memory on a narrow machine for an object-oriented language. In Proceedings of the Conference on Object-Oriented Programming Systems, Languages, and Applications (Portland, OR, Sept. 1986), ACM, pp. 87--106.

....a clean page, but because of swizzling there may be direct memory pointers to the storage previously occupied by the object. So when an object is shrunk, it is replaced by a surrogate, a small data structure containing only the information needed to refetch the object if needed (cf. leaves in LOOM[6], forwarders in Mneme[10] The surrogate ensures that any attempt to use a shrunk object causes the object to be refetched. When a garbage collector fails to reclaim enough space, it can shrink some objects and then proceed. The combination of shrinking and garbage collection is quite robust. In ....

Ted Kaehler. Virtual memory on a narrow machine for an object-oriented language. In ObjectOriented Programming Systems, Languages, and Applications (OOPSLA), pages 87--106, 1986.

....than can be addressed directly by the available hardware. 1 Dealing with this problem involves converting persistent store OIDs into virtual memory addresses, a process which has been termed swizzling [18] This technique originated in early attempts to extend the address space of Smalltalk 80 [11, 12]. In any case, it relies on an OID tovirtual address mapping, maintained in our case by the object store software on behalf of the application. 2.2.3 Database checkpointing Modifications made to persistent data by a persistent program become permanent only when some sort of checkpoint operation ....

T. Kaehler. Virtual memory on a narrow machine for an object-oriented language. In Proceedings of the Conference on Object-Oriented Programming Systems, Languages, and Applications, pages 87--106, Portland, Oregon, Sept. 1986. ACM SIGPLAN Not. 21, 11 (Nov. 1986).

....which will be the building blocks of execution plans. We call this low level object manipulation interface the Object Manager (OM) interface. Object managers have received attention lately in the context of distributed systems [BHJL86, DLA88, MG89, VKC86] programming environments [Dec86, Kae86, VBD89] and databases [CDRS86, CM84, EE87, HZ87, KBC 88] These object managers are typically oriented towards one at atime object execution and differ in terms of their support for data abstraction, concurrency and object distribution. Encapsulation of objects, which hides their ....

T. Kaehler. Virtual memory on a narrow machine for an object-oriented language. In OOPSLA '86 Conference Proceedings, pages 87--106, September 1986.

....which will be the building blocks of execution plans. We call this low level object manipulation interface the Object Manager (OM) interface. Object managers have received attention lately in the context of distributed systems [BHJL86, DLA88, MG89, VKC86] programming environments [Dec86, Kae86] and databases [CDRS86, CM84, EE87, HZ87, KBC 88, VBD89] These object managers differ in terms of their support for data abstraction, concurrency, and object distribution. In addition, they are typically oriented towards one at a time object execution which is an inefficient paradigm for ....

T. Kaehler. Virtual memory on a narrow machine for an object-oriented language. In OOPSLA '86 Conference Proceedings, pages 87--106, September 1986.

....with systems in which oids are not virtual memory addresses. The central question we explore is whether it is profitable to replace oid references between memory resident persistent objects with direct pointers. Such conversion is called pointer swizzling; similar techniques were used in LOOM [2, 3]. The basic tradeoff in swizzling is obvious: the conversion costs something up front (and at the end of the program, to convert pointers back to oids) but saves a little each time a reference is followed. While the qualitative situation is clear, we want to confirm it and describe the tradeoff ....

....objects from the store server format to a faster in memory format. POSs and storage managers include the Exodus storage manager [23, 32] O 2 [29] and Mneme 4 [33, 34, 35] Mneme is the POS used for this study. There have also been a number of designs related to virtual memory such as [2, 3, 36, 37, 38]. Object servers include ObServer [39] and Gemstone [40] We know of no prior studies of swizzling performance, and hence can offer no comparison with directly related work. Published OODB benchmarks and performance studies include [41, 42, 43, 44, 45, 46] 1.2 Simplifying assumptions To study ....

T. Kaehler, "Virtual memory on a narrow machine for an object-oriented language," in OOPSLA [50], pp. 87--106.

....perhaps with a temporary mapping) and must generally be treated differently from addressable local objects. In a few systems, compiler support has been integrated with a sophisticated run time environment to provide the appearance of uniform naming in a very large name space. The LOOM system [28] implements a 32 bit Smalltalk environment on a 16 bit machine. The Emerald system [27] provides a uniform object model on a distributed network of machines. The term pointer swizzling is used to describe systems that transparently manage two distinct sets of addresses for objects: long addresses ....

T. Kaehler, "Virtual Memory on a Narrow Machine for an Object-Oriented Language," OOPSLA'86 Conference Proceedings, 29 September - 2 October 1986, pp. 87-106. In ACM SIGPLAN Notices 21:11.

....of the virtual address space. Extending the size of the heap beyond that which can be addressed in virtual memory requires OIDs that are not virtual memory addresses. Such systems must ultimately perform translation of OIDs to in memory pointers to allow the program to manipulate the data. LOOM [12, 11] represents one of the earliest attempts to extend the size of the heap beyond that addressable by a machine word. Its goal was to provide extended virtual memory support for Smalltalk systems on machines with a narrow (16 bit) word width. Object pointers are stored in 32 bits on disk, and an ....

T. Kaehler. Virtual memory on a narrow machine for an object-oriented language. In Proceedings of the Conference on Object-Oriented Programming Systems, Languages, and Applications, pages 87--106, Portland, Oregon, Sept. 1986. ACM SIGPLAN Not. 21, 11 (Nov. 1986).

No context found.

Ted Kaehler. Virtual memory on a narrow machine for an object-oriented language. In Meyrowitz [Meyrowitz1986], pages 87--106.

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