Bruce Martin, Charles Bergan, and Brian Russ, `PARPC: A System for Parallel Procedure Calls', Proceedings of the 1987 International Conference on Parallel Processing, 449--452 (1987).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the client process to synchronize with the results of such parallel calls. The first version of the Nexus RPC facility, which we implemented in 1988, supported this concept of asynchronous calls [14] Several other RPC systems have also supported asynchronous remote procedure calls [30] 31] [32] [33] and have demonstrated the benefits of such as a facility. A survey of various asynchronous RPC facilities is presented in reference [34] most of these systems were developed in periods overlapping or following the development of the Nexus RPC system. Some of these systems are limited in ....

Bruce Martin, Charles Bergan, and Brian Russ, `PARPC: A System for Parallel Procedure Calls', Proceedings of the 1987 International Conference on Parallel Processing, 449--452 (1987).

....in calling and running remote procedures. To avoid concerning programmers with these details, we have implemented a stub compiler to generate the code required to execute remote procedures. It is similar to the idea presented by Martin, et al. in their parallel remote procedure call package [29] and Reid s RPCC stub compiler [36] Our stub compiler uses the keywords, remote and external as indications of which set of run time library routines the application must call. The stub compiler generates server and client stub routines that consist primarily of run time library function calls. ....

....[3] One example is the PARPC system presented by Martin et al. which calls several procedures in parallel and blocks only until one of the results returns. A client processes the results from the single invocation and then resumes its blocked state until another invocation returns a result [29]. A way for us to approach the problem of asynchronous procedure calls would be to add a type specifier to the ANSIC language that will indicate an asynchronous remote procedure call. This would cause the stub compiler to create stubs that excluded the return process. This way, the transparency of ....

B. Martin, C. Bergan, and B. Russ. PARPC: a system for parallel procedure calls. In Proceedings of the International Conference on Parallel Processing. IEEE, 1987.

....and many distributed software maintenance tasks. The remote procedure call [BiNe84] does not lend itself well to express these semantics as it can only model interactions between a single client and a single server [TaRe85] The parallel procedure call was developed to overcome this limitation [MaBeRu87, Saty86]. A parallel procedure call allows a client process to request the parallel execution of the same procedure in n different address spaces in parallel. We present in this paper our experience in designing and using the PARPC system [MaBeRu87] a parallel remote procedure call system developed at ....

....call was developed to overcome this limitation [MaBeRu87, Saty86] A parallel procedure call allows a client process to request the parallel execution of the same procedure in n different address spaces in parallel. We present in this paper our experience in designing and using the PARPC system [MaBeRu87], a parallel remote procedure call system developed at the University of California, San Diego. The PARPC system came about as a result of the development of the Gemini file system testbed [BuMaPa87] Gemini was built for experimenting with protocols maintaining the consistency of replicated ....

[Article contains additional citation context not shown here]

Martin, B. E., Bergan, C.A., and Russ, Brian, "PARPC: A System for Parallel Procedure Calls" Proceedings of the 1987 International Conference on Parallel Processing, The Pennsylvania State University Press.

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