| 842 |
\end{figure} |
\end{figure} |
| 843 |
|
|
| 844 |
\subsubsection{Multi-threaded execution} |
\subsubsection{Multi-threaded execution} |
| 845 |
|
\label{sec:multi-threaded-execution} |
| 846 |
Prior to transferring control to the procedure {\em THE\_MODEL\_MAIN()} the |
Prior to transferring control to the procedure {\em THE\_MODEL\_MAIN()} the |
| 847 |
WRAPPER may cause several coarse grain threads to be initialized. The routine |
WRAPPER may cause several coarse grain threads to be initialized. The routine |
| 848 |
{\em THE\_MODEL\_MAIN()} is called once for each thread and is passed a single |
{\em THE\_MODEL\_MAIN()} is called once for each thread and is passed a single |
| 930 |
} \\ |
} \\ |
| 931 |
|
|
| 932 |
\subsubsection{Multi-process execution} |
\subsubsection{Multi-process execution} |
| 933 |
|
\label{sec:multi-process-execution} |
| 934 |
|
|
| 935 |
Despite its appealing programming model, multi-threaded execution remains |
Despite its appealing programming model, multi-threaded execution remains |
| 936 |
less common then multi-process execution. One major reason for this |
less common then multi-process execution. One major reason for this |
| 942 |
|
|
| 943 |
Multi-process execution is more ubiquitous. |
Multi-process execution is more ubiquitous. |
| 944 |
In order to run code in a multi-process configuration a decomposition |
In order to run code in a multi-process configuration a decomposition |
| 945 |
specification is given ( in which the at least one of the |
specification ( see section \ref{sec:specifying_a_decomposition}) |
| 946 |
|
is given ( in which the at least one of the |
| 947 |
parameters {\em nPx} or {\em nPy} will be greater than one) |
parameters {\em nPx} or {\em nPy} will be greater than one) |
| 948 |
and then, as for multi-threaded operation, |
and then, as for multi-threaded operation, |
| 949 |
appropriate compile time and run time steps must be taken. |
appropriate compile time and run time steps must be taken. |