insert_task.doxy 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170
  1. /*
  2. * This file is part of the StarPU Handbook.
  3. * Copyright (C) 2009--2011 Universit@'e de Bordeaux
  4. * Copyright (C) 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 CNRS
  5. * Copyright (C) 2011, 2012 INRIA
  6. * See the file version.doxy for copying conditions.
  7. */
  8. /*! \defgroup API_Insert_Task Task Insert Utility
  9. \fn int starpu_insert_task(struct starpu_codelet *cl, ...)
  10. \ingroup API_Insert_Task
  11. Similar to starpu_task_insert(). Kept to avoid breaking old codes.
  12. \fn int starpu_task_insert(struct starpu_codelet *cl, ...)
  13. \ingroup API_Insert_Task
  14. Create and submit a task corresponding to \p cl with the
  15. following given arguments. The argument list must be zero-terminated.
  16. The arguments following the codelet can be of the following types:
  17. <ul>
  18. <li> ::STARPU_R, ::STARPU_W, ::STARPU_RW, ::STARPU_SCRATCH,
  19. ::STARPU_REDUX an access mode followed by a data handle;
  20. <li> ::STARPU_DATA_ARRAY followed by an array of data handles and its
  21. number of elements;
  22. <li> ::STARPU_DATA_MODE_ARRAY followed by an array of struct
  23. starpu_data_descr, i.e data handles with their associated access
  24. modes, and its number of elements;
  25. <li> ::STARPU_EXECUTE_ON_WORKER, ::STARPU_WORKER_ORDER followed by an integer value
  26. specifying the worker on which to execute the task (as specified by
  27. starpu_task::execute_on_a_specific_worker)
  28. <li> the specific values ::STARPU_VALUE, ::STARPU_CALLBACK,
  29. ::STARPU_CALLBACK_ARG, ::STARPU_CALLBACK_WITH_ARG, ::STARPU_PRIORITY,
  30. ::STARPU_TAG, ::STARPU_TAG_ONLY, ::STARPU_FLOPS, ::STARPU_SCHED_CTX, ::STARPU_CL_ARGS, ::STARPU_CL_ARGS_NFREE,
  31. followed by the appropriated objects as defined elsewhere.
  32. </ul>
  33. When using ::STARPU_DATA_ARRAY, the access mode of the data handles is
  34. not defined, it will be taken from the codelet starpu_codelet::modes or starpu_codelet::dyn_modes field. One
  35. should use ::STARPU_DATA_MODE_ARRAY to define the data handles along with the
  36. access modes.
  37. Parameters to be passed to the codelet implementation are defined
  38. through the type ::STARPU_VALUE. The function
  39. starpu_codelet_unpack_args() must be called within the codelet
  40. implementation to retrieve them.
  41. \def STARPU_VALUE
  42. \ingroup API_Insert_Task
  43. Used when calling starpu_task_insert(), must
  44. be followed by a pointer to a constant value and the size of the
  45. constant
  46. \def STARPU_CL_ARGS
  47. \ingroup API_Insert_Task
  48. Used when calling starpu_task_insert(), must
  49. be followed by a memory buffer containing the arguments to be given to
  50. the task, and by the size of the arguments. The memory buffer should
  51. be the result of a previous call to starpu_codelet_pack_args(), and will be
  52. freed (i.e. starpu_task::cl_arg_free will be set to 1)
  53. \def STARPU_CL_ARGS_NFREE
  54. \ingroup API_Insert_Task
  55. Used when calling starpu_task_insert(), similarly to ::STARPU_CL_ARGS, must
  56. be followed by a memory buffer containing the arguments to be given to
  57. the task, and by the size of the arguments. The memory buffer should
  58. be the result of a previous call to starpu_codelet_pack_args(), and will NOT be
  59. freed (i.e. starpu_task::cl_arg_free will be set to 0)
  60. \def STARPU_CALLBACK
  61. \ingroup API_Insert_Task
  62. Used when calling starpu_task_insert(), must
  63. be followed by a pointer to a callback function
  64. \def STARPU_CALLBACK_WITH_ARG
  65. \ingroup API_Insert_Task
  66. Used when calling starpu_task_insert(), must
  67. be followed by two pointers: one to a callback function, and the other
  68. to be given as an argument to the callback function; this is
  69. equivalent to using both ::STARPU_CALLBACK and
  70. ::STARPU_CALLBACK_WITH_ARG.
  71. \def STARPU_CALLBACK_ARG
  72. \ingroup API_Insert_Task
  73. Used when calling starpu_task_insert(), must
  74. be followed by a pointer to be given as an argument to the callback
  75. function
  76. \def STARPU_PRIORITY
  77. \ingroup API_Insert_Task
  78. Used when calling starpu_task_insert(), must
  79. be followed by a integer defining a priority level
  80. \def STARPU_DATA_ARRAY
  81. \ingroup API_Insert_Task
  82. TODO
  83. \def STARPU_DATA_MODE_ARRAY
  84. \ingroup API_Insert_Task
  85. TODO
  86. \def STARPU_EXECUTE_ON_WORKER
  87. \ingroup API_Insert_Task
  88. Used when calling starpu_task_insert(), must be
  89. followed by an integer value specifying the worker on which to execute
  90. the task (as specified by starpu_task::execute_on_a_specific_worker)
  91. \def STARPU_WORKER_ORDER
  92. \ingroup API_Insert_Task
  93. used when calling starpu_task_insert(), must be
  94. followed by an integer value specifying the worker order in which to execute
  95. the tasks (as specified by starpu_task::workerorder)
  96. \def STARPU_TAG
  97. \ingroup API_Insert_Task
  98. Used when calling starpu_task_insert(), must be followed by a tag.
  99. \def STARPU_TAG_ONLY
  100. \ingroup API_Insert_Task
  101. Used when calling starpu_task_insert(), must be followed by a tag
  102. stored in starpu_task::tag_id. Leave starpu_task::use_tag as 0.
  103. \def STARPU_NAME
  104. \ingroup API_Insert_Task
  105. Used when calling starpu_task_insert(), must be followed by a char *
  106. stored in starpu_task::name.
  107. \def STARPU_FLOPS
  108. \ingroup API_Insert_Task
  109. Used when calling starpu_task_insert(), must
  110. be followed by an amount of floating point operations, as a double.
  111. Users <b>MUST</b> explicitly cast into double, otherwise parameter
  112. passing will not work.
  113. \def STARPU_SCHED_CTX
  114. \ingroup API_Insert_Task
  115. Used when calling starpu_task_insert(), must
  116. be followed by the id of the scheduling context to which to submit the
  117. task to.
  118. \fn void starpu_codelet_pack_args(void **arg_buffer, size_t *arg_buffer_size, ...)
  119. \ingroup API_Insert_Task
  120. Pack arguments of type ::STARPU_VALUE into a buffer which can be
  121. given to a codelet and later unpacked with the function
  122. starpu_codelet_unpack_args().
  123. \fn void starpu_codelet_unpack_args(void *cl_arg, ...)
  124. \ingroup API_Insert_Task
  125. Retrieve the arguments of type ::STARPU_VALUE associated to a
  126. task automatically created using the function starpu_task_insert(). If
  127. any parameter's value is 0, unpacking will stop there and ignore the remaining
  128. parameters.
  129. \fn void starpu_codelet_unpack_args_and_copyleft(void *cl_arg, void *buffer, size_t buffer_size, ...)
  130. \ingroup API_Insert_Task
  131. Similar to starpu_codelet_unpack_args(), but if any parameter is
  132. 0, copy the part of \p cl_arg that has not been read in \p buffer which
  133. can then be used in a later call to one of the unpack functions.
  134. \fn struct starpu_task *starpu_task_build(struct starpu_codelet *cl, ...)
  135. \ingroup API_Insert_Task
  136. Create a task corresponding to \p cl with the following arguments.
  137. The argument list must be zero-terminated. The arguments
  138. following the codelet are the same as the ones for the function
  139. starpu_task_insert().
  140. If some arguments of type ::STARPU_VALUE are given, the parameter
  141. starpu_task::cl_arg_free will be set to 1.
  142. */