Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Parallel Computing, 20:547-564, April 1994. (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....are commonly used on many types of machines, ranging from massively parallel supercomputers to clusters of workstations. The reader is assumed here to have a significant knowledge of the de facto MPI 1 standard [14, 15] an effort influenced by over a decade of research and commercial systems [2, 3, 7, 11, 12, 19, 21, 23, 24, 25, 27, 29]. This interface has been realized in several commercial implementations, based on well known public implementations [5, 20] In this paper, we present two object oriented class libraries for supplementing MPI, in support of C . The features and limitations of these systems are indicated, as is ....

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: the p4 parallel programming system. Journal of Parallel Computing, 1994. to appear (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

....interoperability in the near future. TCP IP interoperability is the logical first candidate. Under such consideration, these, among other issues could be raised: 1. Registering common ports for messaging and process management with IETF 2. Agreeing on interoperable headers (e.g. unify p4 type [1, 2], lam type, msti type) 3. Agreement on protocols for message lengths (short, long, very long) 4. Agreement on concensus for context establishment 5. Agreement on minimal concensus for collective 6. Agreement on well known services for remote process management (daemonology, including security) 7. ....

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Parallel Computing, 20:547--564, April 1994. (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

No context found.

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Parallel Computing, 20:547-564, April 1994. (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

....We focus here on what can be accomplished with this basic set of tools, and consider higher level constructs to be built on these. The idea of combining the shared memory and message passing models is not new. It has been described in [1] and implemented in a widely available programming system [2]. However, the current computing environment, with this programming model becoming available in so many different ways, gives the topic renewed importance. In Section 2, we define the terms we will use in our discussion of programming models. Section 3 briefly describes the criteria we will use ....

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Parallel Computing, 20:547--564, April 1994. (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

....device speci cation (ADI) described in [5] In some environments, this abstract device is con gured to be the native communication subsystem of the machine. This is done with the device argument to configure. For the rest of the environments, a generic communication device is constructed using p4 [1, 2] and that is used as the instantiation of the ADI. In these cases, use ch p4 as the device. The ARCH TYPE speci es what kind of processor the compilations will take place on. Valid ones are listed above. For the IBM SP, the architecture type is rs6000. If not given, configure will attempt to ....

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Parallel Computing, 20:547-564, April 1994. (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

....specification (ADI) described in [3] In some environments, this abstract device is configured to be the native communication subsystem of the machine. This is done with the device argument to configure. For the rest of the environments, a generic communication device is constructed using p4 [1, 2] and that is used as the instantiation of the ADI. In these cases, use chp4 as the device. The ARCHTYPE specifies what kind of processor the compilations will take place on. Valid ones are listed above. For the IBM SP, the architecture type is rs6000. If not given, configure will attempt to ....

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Parallel Computing, 20:547--564, April 1994. (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

....device speci cation (ADI) described in [4] In some environments, this abstract device is con gured to be the native communication subsystem of the machine. This is done with the device argument to configure. For the rest of the environments, a generic communication device is constructed using p4 [1, 2] and that is used as the instantiation of the ADI. In these cases, use ch p4 as the device. The ARCH TYPE speci es what kind of processor the compilations will take place on. Valid ones are listed above. For the IBM SP, the architecture type is rs6000. If not given, configure will attempt to ....

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Parallel Computing, 20:547-564, April 1994. (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

.... sx, sy, sz, ex, ey, ez; int sxgp, sygp, szgp, exgp, eygp, ezgp; double hlx, hly, hlz, ps; PIFILE fp; PIFArrayPart sz[3] sz[0] mdim = nx; sz[0] ndim = ex exgp sx sxgp 1; sz[0] start = sxgp; sz[0] end = sxgp ex sx ; sz[0] gstart = sx sxgp; sz[0] gend = ex exgp; sz[1].mdim = ny; sz[1] ndim = ey eygp sy sygp 1; sz[1] start = sygp; sz[1] end = sygp ey sy; sz[1] gstart = sy sygp; sz[1] gend = ey eygp; sz[2] mdim = nz; sz[2] ndim = ez ezgp sz szgp 1; sz[2] start = szgp; sz[2] end = szgp ez sz; sz[2] gstart = sz szgp; sz[2] gend = ez ....

.... ex, ey, ez; int sxgp, sygp, szgp, exgp, eygp, ezgp; double hlx, hly, hlz, ps; PIFILE fp; PIFArrayPart sz[3] sz[0] mdim = nx; sz[0] ndim = ex exgp sx sxgp 1; sz[0] start = sxgp; sz[0] end = sxgp ex sx ; sz[0] gstart = sx sxgp; sz[0] gend = ex exgp; sz[1] mdim = ny; sz[1].ndim = ey eygp sy sygp 1; sz[1] start = sygp; sz[1] end = sygp ey sy; sz[1] gstart = sy sygp; sz[1] gend = ey eygp; sz[2] mdim = nz; sz[2] ndim = ez ezgp sz szgp 1; sz[2] start = szgp; sz[2] end = szgp ez sz; sz[2] gstart = sz szgp; sz[2] gend = ez ezgp; fp = ....

[Article contains additional citation context not shown here]

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Journal of Parallel Computing. to appear (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

....process. This implementation obtains portability without giving up efficiency by the use of an Abstract Device Interface (ADI) that renders most of the implementation portable and thus usable by others [10] It currently runs directly on several parallel supercomputers (IBM, Intel, TMC) and via p4 [3] and PVM [7] on other parallel machines and workstation networks. Greg Burns, Ohio Supercomputer Center. LAM is an implementation of MPI for workstations layered on the Trollius distributed system. The talk stimulated discussion of the progress rules in the Standard, and whether they could be ....

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Parallel Computing, 20:547--564, April 1994. (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

....so the usual Chameleon methods of preparing programs and starting jobs apply. There are man pages for all of the MPI routines in usr local mpi man . Supported Transport Layers: Switch IP, Switch US, Ethernet IP. Contact: gropp mcs.anl.gov or lusk mcs.anl.gov for more information. 3.2. 5 p4 p4 [2, 1] is a portable message passing system that runs on a very wide variety of parallel systems and workstations. It is in use at approximately 200 sites around the world. Existing p4 programs will run unchanged on the SPx. The current version is version 1.4, but experimental versions (such as 1.4a) ....

Ralph Butler and Ewing Lusk. Monitors, messages, and clusters: The p4 parallel programming system. Journal of Parallel Computing, 1993. To appear (Also Argonne National Laboratory Mathematics and Computer Science Division preprint P362-0493).

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