7 citations found. Retrieving documents...
Hempel, R., Hoppe, H.-C., and Supalov, A. A Proposal for a PARMACS library interface. Technical Report, October 1992.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
A Draft Standard For Message Passing In A Distributed Memory .. - Dongarra Hempelz (1993)   (2 citations)  (Correct)

....existing message passing systems, rather than selecting one of them and adopting it as the standard. Thus, MPI1 has been strongly influenced by work at the IBM T. J. Watson Research Center by Bala, Kipnis, Snir and colleagues [1,2] Intel s NX 2 [17] Express [16] nCUBE s Vertex [14] and PARMACS [11,12]. Other important contributions have come from Zipcode [18,19] Chimp [6,7] PVM [8,20] and PICL [9] One of the objectives of this paper is to promote a discussion within the concurrent computing research community of the issues that must be addressed in establishing a practical, portable, and ....

....of the message packing routines; and so on. If the integer returned by MPI ERROR is passed to the routine MPI ETEXT, a string is returned giving a short description of the error which can then be output by the application. This way of handling errors is essentially the same as that used by PARMACS [12]. 4. DISCUSSION AND RATIONALE In this section we discuss the reasoning behind some of the decisions made in designing MPI1. In the design of this interface, one of the main concerns was to keep both the calling sequences simple and the range of options limited, while at the same time maintaining ....

R. Hempel, H.-C. Hoppe, and A. Supalov, "A Proposal for a PARMACS Library Interface," GMD, Postfach 1316, D-5205 Sankt Augustin 1, Germany (October 1992).


The Design Of A Standard Message Passing Interface For.. - Walker (1994)   (52 citations)  (Correct)

....provide hardware or low level system support for, thereby enhancing scalability. The functionality that mpi is designed to provide is based on current common practice, and is similar to that provided by widely used message passing systems such as Express [12] NX 2 [13] Vertex, 11] parmacs [8, 9], and P4 [10] In addition, the flexibility and usefulness of mpi has been broadened by incorporating ideas from more recent and innovative message passing systems such as chimp [4, 5] Zipcode [14, 15] and the IBM External User Interface [7] The general design philosophy followed by mpi is that ....

R. Hempel, H.-C. Hoppe, and A. Supalov. A proposal for a PARMACS library interface. Technical report, GMD, Postfach 1316, D-5205 Sankt Augustin 1, Germany, October 1992.


On the Software Engineering of Multi-Platform.. - Markus, Catlin..   (Correct)

....components of ELLPACK execute using the message passing model. The original ELLPACK solvers were developed primarily for an nCUBE 2 machine using nCUBE s native communication library (VERTEX [9] We have now migrated this code to several communication libraries, including PICL [4] PARMACS [10] and several MPI [6] implementations as well as to other hardware platforms. Ports to PVM [8] and Intel NX [11] are currently underway. Since most of these communication libraries are not universally portable, the communication libraries supported are dependent on the hardware platform; for ....

R. Hempel, H.-C. Hoppe and A. Supalov, "A proposal for a PARMACS library interface," Technical Report, GMD, Postfach 1316, D-5205 Sankt Augustin 1, Germany, October 1992.


MPI: A Message Passing Interface - Forum (1993)   (57 citations)  (Correct)

....hardware or low level system support for, thereby enhancing scalability. The functionality that mpi is designed to provide is based on current common practice, and is similar to that provided by widely used message passing systems such as Express [15] PVM [2] NX 2 [16] Vertex, 14] parmacs [10, 11], and P4 [4, 13] In addition, the flexibility and usefulness of mpi has been broadened by incorporating ideas from more recent and innovative message passing systems such as chimp [6, 7] Zipcode [17, 18] and the IBM External User Interface [8] The general design philosophy followed by mpi is ....

R. Hempel, H.-C. Hoppe, and A. Supalov. A proposal for a PARMACS library interface. Technical report, GMD, Postfach 1316, D-5205 Sankt Augustin 1, Germany, October 1992.


MPI: A Standard Message Passing Interface - Walker, Dongarra (1996)   (8 citations)  (Correct)

....provide hardware or low level system support for, thereby enhancing scalability. The functionality that MPI is designed to provide is based on current common practice, and is similar to that provided by widely used message passing systems such as Express [11] NX 2 [12] Vertex, 10] parmacs [7, 8], and P4 [9] In addition, the flexibility and usefulness of MPI has been broadened by incorporating ideas from more recent and innovative message passing systems such as chimp [4, 5] Zipcode [13, 14] and the IBM External User Interface [6] The MPI standardization effort involved about 60 ....

R. Hempel, H.-C. Hoppe, and A. Supalov. A proposal for a PARMACS library interface. Technical report, GMD, Postfach 1316, D-5205 Sankt Augustin 1, Germany, October 1992.


A Proposal For A User-Level, Message Passing Interface In.. - Dongarra, Hempel, al. (1993)   (25 citations)  Self-citation (Hempel)   (Correct)

....message passing systems, rather than selecting one of them and adopting it as the standard. Thus, MPI1 has been strongly influenced by work at the IBM T. J. Watson Research Center by Bala, Kipnis, Snir and colleagues [2, 3] Intel s NX 2 [18] Express [17] nCUBE s Vertex [15] and PARMACS [11, 13]. Other important contributions have come from Zipcode [19, 20] Chimp [6, 7] PVM [8, 21] and PICL [9] One of the objectives of this paper is to promote a discussion within the concurrent computing research community of the issues that must be addressed in establishing a practical, portable, ....

....of the message packing routines; and so on. If the integer returned by MPI ERROR is passed to the routine MPI ETEXT, a string is returned giving a short description of the error which can then be output by the application. This way of handling errors is essentially the same as that used by PARMACS [13]. 4. Discussion and Rationale In this section we discuss the reasoning behind some of the decisions made in designing MPI1. In the design of this interface, one of the main concerns was to keep both the calling sequences simple and the range of options limited, while at the same time maintaining ....

R. Hempel, H.-C. Hoppe, and A. Supalov. A proposal for a PARMACS library interface. Technical report, GMD, Postfach 1316, D-5205 Sankt Augustin 1, Germany, October 1992.


A Parallelizing Compiler for a Cluster of - Workstations In Partial (1998)   (Correct)

No context found.

Hempel, R., Hoppe, H.-C., and Supalov, A. A Proposal for a PARMACS library interface. Technical Report, October 1992.

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