mpi.doxy 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293
  1. /*
  2. * This file is part of the StarPU Handbook.
  3. * Copyright (C) 2009--2011 Universit@'e de Bordeaux 1
  4. * Copyright (C) 2010, 2011, 2012, 2013 Centre National de la Recherche Scientifique
  5. * Copyright (C) 2011, 2012 Institut National de Recherche en Informatique et Automatique
  6. * See the file version.doxy for copying conditions.
  7. */
  8. /*! \defgroup API_MPI_Support MPI Support
  9. @name Initialisation
  10. \ingroup API_MPI_Support
  11. \fn int starpu_mpi_init(int *argc, char ***argv, int initialize_mpi)
  12. \ingroup API_MPI_Support
  13. Initializes the starpumpi library. \p initialize_mpi indicates if MPI
  14. should be initialized or not by StarPU. If the value is not 0, MPI
  15. will be initialized by calling <c>MPI_Init_Thread(argc, argv,
  16. MPI_THREAD_SERIALIZED, ...)</c>.
  17. \fn int starpu_mpi_initialize(void)
  18. \deprecated
  19. \ingroup API_MPI_Support
  20. This function has been made deprecated. One should use instead the
  21. function starpu_mpi_init(). This function does not call MPI_Init(), it
  22. should be called beforehand.
  23. \fn int starpu_mpi_initialize_extended(int *rank, int *world_size)
  24. \deprecated
  25. \ingroup API_MPI_Support
  26. This function has been made deprecated. One should use instead the
  27. function starpu_mpi_init(). MPI will be initialized by starpumpi by
  28. calling <c>MPI_Init_Thread(argc, argv, MPI_THREAD_SERIALIZED,
  29. ...)</c>.
  30. \fn int starpu_mpi_shutdown(void)
  31. \ingroup API_MPI_Support
  32. Cleans the starpumpi library. This must be called between calling
  33. starpu_mpi functions and starpu_shutdown(). MPI_Finalize() will be
  34. called if StarPU-MPI has been initialized by starpu_mpi_init().
  35. \fn void starpu_mpi_comm_amounts_retrieve(size_t *comm_amounts)
  36. \ingroup API_MPI_Support
  37. Retrieve the current amount of communications from the current node in
  38. the array \p comm_amounts which must have a size greater or equal to
  39. the world size. Communications statistics must be enabled (see
  40. \ref STARPU_COMM_STATS).
  41. @name Communication
  42. \anchor MPIPtpCommunication
  43. \ingroup API_MPI_Support
  44. \fn int starpu_mpi_send(starpu_data_handle_t data_handle, int dest, int mpi_tag, MPI_Comm comm)
  45. \ingroup API_MPI_Support
  46. Performs a standard-mode, blocking send of \p data_handle to the node
  47. \p dest using the message tag \p mpi_tag within the communicator \p
  48. comm.
  49. \fn int starpu_mpi_recv(starpu_data_handle_t data_handle, int source, int mpi_tag, MPI_Comm comm, MPI_Status *status)
  50. \ingroup API_MPI_Support
  51. Performs a standard-mode, blocking receive in \p data_handle from the
  52. node \p source using the message tag \p mpi_tag within the
  53. communicator \p comm.
  54. \fn int starpu_mpi_isend(starpu_data_handle_t data_handle, starpu_mpi_req *req, int dest, int mpi_tag, MPI_Comm comm)
  55. \ingroup API_MPI_Support
  56. Posts a standard-mode, non blocking send of \p data_handle to the node
  57. \p dest using the message tag \p mpi_tag within the communicator \p
  58. comm. After the call, the pointer to the request \p req can be used to
  59. test or to wait for the completion of the communication.
  60. \fn int starpu_mpi_irecv(starpu_data_handle_t data_handle, starpu_mpi_req *req, int source, int mpi_tag, MPI_Comm comm)
  61. \ingroup API_MPI_Support
  62. Posts a nonblocking receive in \p data_handle from the node \p source
  63. using the message tag \p mpi_tag within the communicator \p comm.
  64. After the call, the pointer to the request \p req can be used to test
  65. or to wait for the completion of the communication.
  66. \fn int starpu_mpi_isend_detached(starpu_data_handle_t data_handle, int dest, int mpi_tag, MPI_Comm comm, void (*callback)(void *), void *arg)
  67. \ingroup API_MPI_Support
  68. Posts a standard-mode, non blocking send of \p data_handle to the node
  69. \p dest using the message tag \p mpi_tag within the communicator \p
  70. comm. On completion, the \p callback function is called with the
  71. argument \p arg.
  72. Similarly to the pthread detached functionality, when a detached
  73. communication completes, its resources are automatically released back
  74. to the system, there is no need to test or to wait for the completion
  75. of the request.
  76. \fn int starpu_mpi_irecv_detached(starpu_data_handle_t data_handle, int source, int mpi_tag, MPI_Comm comm, void (*callback)(void *), void *arg)
  77. \ingroup API_MPI_Support
  78. Posts a nonblocking receive in \p data_handle from the node \p source
  79. using the message tag \p mpi_tag within the communicator \p comm. On
  80. completion, the \p callback function is called with the argument \p
  81. arg.
  82. Similarly to the pthread detached functionality, when a detached
  83. communication completes, its resources are automatically released back
  84. to the system, there is no need to test or to wait for the completion
  85. of the request.
  86. \fn int starpu_mpi_irecv_detached_sequential_consistency(starpu_data_handle_t data_handle, int source, int mpi_tag, MPI_Comm comm, void (*callback)(void *), void *arg, int sequential_consistency)
  87. \ingroup API_MPI_Support
  88. Posts a nonblocking receive in \p data_handle from the node \p source
  89. using the message tag \p mpi_tag within the communicator \p comm. On
  90. completion, the \p callback function is called with the argument \p
  91. arg.
  92. The parameter \p sequential_consistency allows to enable or disable
  93. the sequential consistency for \p data handle (sequential consistency
  94. will be enabled or disabled based on the value of the parameter \p
  95. sequential_consistency and the value of the sequential consistency
  96. defined for \p data_handle).
  97. Similarly to the pthread detached functionality, when a detached
  98. communication completes, its resources are automatically released back
  99. to the system, there is no need to test or to wait for the completion
  100. of the request.
  101. \fn int starpu_mpi_wait(starpu_mpi_req *req, MPI_Status *status)
  102. \ingroup API_MPI_Support
  103. Returns when the operation identified by request \p req is complete.
  104. \fn int starpu_mpi_test(starpu_mpi_req *req, int *flag, MPI_Status *status)
  105. \ingroup API_MPI_Support
  106. If the operation identified by \p req is complete, set \p flag to 1.
  107. The \p status object is set to contain information on the completed
  108. operation.
  109. \fn int starpu_mpi_barrier(MPI_Comm comm)
  110. \ingroup API_MPI_Support
  111. Blocks the caller until all group members of the communicator \p comm
  112. have called it.
  113. \fn int starpu_mpi_isend_detached_unlock_tag(starpu_data_handle_t data_handle, int dest, int mpi_tag, MPI_Comm comm, starpu_tag_t tag)
  114. \ingroup API_MPI_Support
  115. Posts a standard-mode, non blocking send of \p data_handle to the node
  116. \p dest using the message tag \p mpi_tag within the communicator \p
  117. comm. On completion, \p tag is unlocked.
  118. \fn int starpu_mpi_irecv_detached_unlock_tag(starpu_data_handle_t data_handle, int source, int mpi_tag, MPI_Comm comm, starpu_tag_t tag)
  119. \ingroup API_MPI_Support
  120. Posts a nonblocking receive in \p data_handle from the node \p source
  121. using the message tag \p mpi_tag within the communicator \p comm. On
  122. completion, \p tag is unlocked.
  123. \fn int starpu_mpi_isend_array_detached_unlock_tag(unsigned array_size, starpu_data_handle_t *data_handle, int *dest, int *mpi_tag, MPI_Comm *comm, starpu_tag_t tag)
  124. \ingroup API_MPI_Support
  125. Posts \p array_size standard-mode, non blocking send. Each post sends
  126. the n-th data of the array \p data_handle to the n-th node of the
  127. array \p dest using the n-th message tag of the array \p mpi_tag
  128. within the n-th communicator of the array \p comm. On completion of
  129. the all the requests, \p tag is unlocked.
  130. \fn int starpu_mpi_irecv_array_detached_unlock_tag(unsigned array_size, starpu_data_handle_t *data_handle, int *source, int *mpi_tag, MPI_Comm *comm, starpu_tag_t tag)
  131. \ingroup API_MPI_Support
  132. Posts \p array_size nonblocking receive. Each post receives in the n-th
  133. data of the array \p data_handle from the n-th node of the array \p
  134. source using the n-th message tag of the array \p mpi_tag within the
  135. n-th communicator of the array \p comm. On completion of the all the
  136. requests, \p tag is unlocked.
  137. @name Communication Cache
  138. \ingroup API_MPI_Support
  139. \fn void starpu_mpi_cache_flush(MPI_Comm comm, starpu_data_handle_t data_handle)
  140. \ingroup API_MPI_Support
  141. Clear the send and receive communication cache for the data
  142. \p data_handle. The function has to be called synchronously by all the
  143. MPI nodes. The function does nothing if the cache mechanism is
  144. disabled (see \ref STARPU_MPI_CACHE).
  145. \fn void starpu_mpi_cache_flush_all_data(MPI_Comm comm)
  146. \ingroup API_MPI_Support
  147. Clear the send and receive communication cache for all data. The
  148. function has to be called synchronously by all the MPI nodes. The
  149. function does nothing if the cache mechanism is disabled (see
  150. \ref STARPU_MPI_CACHE).
  151. @name MPI Insert Task
  152. \anchor MPIInsertTask
  153. \ingroup API_MPI_Support
  154. \fn int starpu_data_set_tag(starpu_data_handle_t handle, int tag)
  155. \ingroup API_MPI_Support
  156. Tell StarPU-MPI which MPI tag to use when exchanging the data.
  157. \fn int starpu_data_get_tag(starpu_data_handle_t handle)
  158. \ingroup API_MPI_Support
  159. Returns the MPI tag to be used when exchanging the data.
  160. \fn int starpu_data_set_rank(starpu_data_handle_t handle, int rank)
  161. \ingroup API_MPI_Support
  162. Tell StarPU-MPI which MPI node "owns" a given data, that is, the node
  163. which will always keep an up-to-date value, and will by default
  164. execute tasks which write to it.
  165. \fn int starpu_data_get_rank(starpu_data_handle_t handle)
  166. \ingroup API_MPI_Support
  167. Returns the last value set by starpu_data_set_rank().
  168. \def STARPU_EXECUTE_ON_NODE
  169. \ingroup API_MPI_Support
  170. this macro is used when calling starpu_mpi_insert_task(), and must be
  171. followed by a integer value which specified the node on which to
  172. execute the codelet.
  173. \def STARPU_EXECUTE_ON_DATA
  174. \ingroup API_MPI_Support
  175. this macro is used when calling starpu_mpi_insert_task(), and must be
  176. followed by a data handle to specify that the node owning the given
  177. data will execute the codelet.
  178. \fn int starpu_mpi_insert_task(MPI_Comm comm, struct starpu_codelet *codelet, ...)
  179. \ingroup API_MPI_Support
  180. Create and submit a task corresponding to codelet with the following
  181. arguments. The argument list must be zero-terminated.
  182. The arguments following the codelets are the same types as for the
  183. function starpu_insert_task(). The extra argument
  184. ::STARPU_EXECUTE_ON_NODE followed by an integer allows to specify the
  185. MPI node to execute the codelet. It is also possible to specify that
  186. the node owning a specific data will execute the codelet, by using
  187. ::STARPU_EXECUTE_ON_DATA followed by a data handle.
  188. The internal algorithm is as follows:
  189. <ol>
  190. <li>
  191. Find out which MPI node is going to execute the codelet.
  192. <ul>
  193. <li>If there is only one node owning data in ::STARPU_W mode, it will be selected;
  194. <li>If there is several nodes owning data in ::STARPU_W node, the one selected will be the one having the least data in R mode so as to minimize the amount of data to be transfered;
  195. <li>The argument ::STARPU_EXECUTE_ON_NODE followed by an integer can be used to specify the node;
  196. <li>The argument ::STARPU_EXECUTE_ON_DATA followed by a data handle can be used to specify that the node owing the given data will execute the codelet.
  197. </ul>
  198. </li>
  199. <li>
  200. Send and receive data as requested. Nodes owning data which need to be read by the task are sending them to the MPI node which will execute it. The latter receives them.
  201. </li>
  202. <li>
  203. Execute the codelet. This is done by the MPI node selected in the 1st step of the algorithm.
  204. </li>
  205. <li>
  206. If several MPI nodes own data to be written to, send written data back to their owners.
  207. </li>
  208. </ol>
  209. The algorithm also includes a communication cache mechanism that
  210. allows not to send data twice to the same MPI node, unless the data
  211. has been modified. The cache can be disabled (see \ref STARPU_MPI_CACHE).
  212. \fn void starpu_mpi_get_data_on_node(MPI_Comm comm, starpu_data_handle_t data_handle, int node)
  213. \ingroup API_MPI_Support
  214. Transfer data \p data_handle to MPI node \p node, sending it from its
  215. owner if needed. At least the target node and the owner have to call
  216. the function.
  217. \fn void starpu_mpi_get_data_on_node_detached(MPI_Comm comm, starpu_data_handle_t data_handle, int node, void (*callback)(void*), void *arg)
  218. \ingroup API_MPI_Support
  219. Transfer data \p data_handle to MPI node \p node, sending it from its
  220. owner if needed. At least the target node and the owner have to call
  221. the function. On reception, the \p callback function is called with
  222. the argument \p arg.
  223. @name Collective Operations
  224. \anchor MPICollectiveOperations
  225. \ingroup API_MPI_Support
  226. \fn void starpu_mpi_redux_data(MPI_Comm comm, starpu_data_handle_t data_handle)
  227. \ingroup API_MPI_Support
  228. Perform a reduction on the given data. All nodes send the data to its
  229. owner node which will perform a reduction.
  230. \fn int starpu_mpi_scatter_detached(starpu_data_handle_t *data_handles, int count, int root, MPI_Comm comm, void (*scallback)(void *), void *sarg, void (*rcallback)(void *), void *rarg)
  231. \ingroup API_MPI_Support
  232. Scatter data among processes of the communicator based on the
  233. ownership of the data. For each data of the array \p data_handles, the
  234. process \p root sends the data to the process owning this data. Processes
  235. receiving data must have valid data handles to receive them. On
  236. completion of the collective communication, the \p scallback function is
  237. called with the argument \p sarg on the process \p root, the \p
  238. rcallback function is called with the argument \p rarg on any other
  239. process.
  240. \fn int starpu_mpi_gather_detached(starpu_data_handle_t *data_handles, int count, int root, MPI_Comm comm, void (*scallback)(void *), void *sarg, void (*rcallback)(void *), void *rarg)
  241. \ingroup API_MPI_Support
  242. Gather data from the different processes of the communicator onto the
  243. process \p root. Each process owning data handle in the array
  244. \p data_handles will send them to the process \p root. The process \p
  245. root must have valid data handles to receive the data. On completion
  246. of the collective communication, the \p rcallback function is called
  247. with the argument \p rarg on the process root, the \p scallback
  248. function is called with the argument \p sarg on any other process.
  249. */