What is MPI?
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj8A9USA6O3sI94jjmZfhwRRA7f1pl_iueJYo1gwhHCSovhSS_0IQwVhlKyzDMayi7BFqlo9tvpZYxevwSX3DFFeJN8OUgf9FcL6lOa4WbVpSCQEYXz34ECSgs-PTCssGArwc0ecY1amNKI/s200/mpi.png)
Functionality
The MPI interface is meant to provide essential virtual topology, synchronization, and communication functionality between a set of processes (that have been mapped to nodes/servers/computer instances) in a language-independent way, with language-specific syntax (bindings), plus a few language-specific features. MPI programs always work with processes, but programmers commonly refer to the processes as processors. Typically, for maximum performance, each CPU (or core in a multi-core machine) will be assigned just a single process. This assignment happens at runtime through the agent that starts the MPI program, normally called mpirun or mpiexec.
What is POSIX?
Short for "Portable Operating System Interface for uni-X", POSIX is a set of standards codified by the IEEE and issued by ANSI and ISO. The goal of POSIX is to ease the task of cross-platform software development by establishing a set of guidelines for operating system vendors to follow. Ideally, a developer should have to write a program only once to run on all POSIX-compliant systems. Most modern commercial Unix implementations and many free ones are POSIX compliant. There are actually several different POSIX releases, but the most important are POSIX.1 and POSIX.2, which define system calls and command-line interface, respectively.
The POSIX specifications describe an operating system that is similar to, but not necessarily the same as, Unix. Though POSIX is heavily based on the BSD and System V releases, non-Unix systems such as Microsoft's Windows NT and IBM's OpenEdition MVS are POSIX compliant.
Aquí va 7 para el lab. Asegúrate que el contenido también se encuentre en el Wiki.
ResponderEliminar