Jakov Seizovic. The Reactive Kernel. Technical Report Caltech-CS-TR-88-10, California Institute of Technology, 1988.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....users could define their own library for an asynchronous collective operation) 3. 2 Porting Strategy Zipcode currently relies on the basic process management (spawn kill) and messaging services (xprimitives) of the Reactive Kernel Cosmic Environment, or, more usually, emulations thereof [5, 6]. This strategy has been effective in that we have produced stable, usable ports for the Symult S2010, nCUBE 2, iPSC 2, iPSC 860, Delta, Paragon, BBN TC2000, CM 5 scalar machine, Sun workstation network, and RS 6000 networks during the past five years. A port to the PVM systems is nearly completed ....

Jakov Seizovic. The Reactive Kernel. Technical Report Caltech-CS-TR-88-10, California Institute of Technology, 1988.

....difficult. First, a direct implementation on MIMD machines is nontrivial. The user must handle the synchronization and load balance issues at the same time, which could be extremely difficult for some application problems. In general, a runtime support system, such as LINDA [2, 5] reactive kernel [27, 33], or chare kernel [30] is necessary for solving asynchronous problems. Implementation of the asynchronous problems on SIMD machines is even more difficult because it needs a runtime support system, and the support system itself is asynchronous. In particular, the support system must arrange the ....

J. Seizovic. The reactive kernel. Technical Report Caltech-CS-TR-99-10, Computer Science, California Institute of Technology, 1988.

....under the auspices of the U. S. Department of Energy by the Lawrence Livermore National Laboratory under contract No. W 7405 ENG 48. Work supported, in part, by the NSF Engineering Research Center for Computational Field Simulation, Mississippi State University. 1 Introduction Zipcode was developed in 1988 at the California Institute of Technology by the first author, and was developed further at Lawrence Livermore National Laboratory, with additions and support continuing to this date at Mississippi State University [29] This message passing system was strongly influenced by the point to point ....

.... first author, and was developed further at Lawrence Livermore National Laboratory, with additions and support continuing to this date at Mississippi State University [29] This message passing system was strongly influenced by the point to point semantics of the Reactive Kernel primitives [23, 24, 25] by the collective primitives of CrOS [15, Chapter 14] and by the process management features of the Cosmic Environment [23] all developed at Caltech) Zipcode includes features that were not found in then existing vendor systems (like NX 2 [22] and portability systems (like PICL [18] Many ....

[Article contains additional citation context not shown here]

Jakov Seizovic. The Reactive Kernel. Technical Report Caltech-CS-TR-88-10, California Institute of Technology, 1988.

....difficult. First, a direct implementation on MIMD machines is nontrivial. The user must handle the synchronization and load balance issues at the same time, which could be extremely difficult for some application problems. In general, a runtime support system, such as LINDA [1] reactive kernel [15], or chare kernel [17] is necessary for solving asynchronous problems. Implementation of the asynchronous problems on SIMD machines is even more difficult because it needs a runtime support system and the support system itself is asynchronous. In particular, the support system must arrange the ....

J. Seizovic. The reactive kernel. Technical Report Caltech-CS-TR-99-10, Computer Science, California Institute of Technology, 1988.

....information in their instructions, nor work over addressee lists, for which special properties may be asserted. 1. 3 Scope of Portability The evolutionary processes described in the foregoing indicate that Zipcode has fully surpassed its original Reactive Kernel Cosmic Environment platform [9, 10, 11]; it is now planned that Zipcode implementations will be based on one or more of the following in a given implementation: ffl Hardware based shared memory, ffl Active message strategies (cf, 22] ffl Pure Message Passing on multicomputers, ffl Control Network operations definable on ....

....could define their own libraries for asynchronous collective operations) 2. 2 Porting Strategy Zipcode has, to now, relied on the basic process management (spawn kill) and messaging services (xprimitives) of the Reactive Kernel Cosmic Environment, or, more usually, our own emulations thereof [9, 10, 11]. This strategy has been effective in that we have produced stable, usable ports for the Symult S2010, nCUBE 2, iPSC 2, iPSC 860, Delta, Paragon, BBN TC2000, CM 5 scalar machine, Sun workstation network, and RS 6000 networks during the past five years. A port to the PVM systems is nearly completed ....

Jakov Seizovic. The Reactive Kernel. Technical Report Caltech-CS-TR-88-10, California Institute of Technology, 1988.

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