scheduling_contexts.doxy 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249
  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_Scheduling_Contexts Scheduling Contexts
  9. \brief StarPU permits on one hand grouping workers in combined workers
  10. in order to execute a parallel task and on the other hand grouping
  11. tasks in bundles that will be executed by a single specified worker.
  12. In contrast when we group workers in scheduling contexts we submit
  13. starpu tasks to them and we schedule them with the policy assigned to
  14. the context. Scheduling contexts can be created, deleted and modified
  15. dynamically.
  16. \enum starpu_worker_collection_type
  17. \ingroup API_Scheduling_Contexts
  18. types of structures the worker collection can implement
  19. \var starpu_worker_collection_type::STARPU_WORKER_LIST
  20. \ingroup API_Scheduling_Contexts
  21. List of workers
  22. \struct starpu_sched_ctx_iterator
  23. \ingroup API_Scheduling_Contexts
  24. todo
  25. \var starpu_sched_ctx_iterator::cursor
  26. todo
  27. \struct starpu_worker_collection
  28. \ingroup API_Scheduling_Contexts
  29. A scheduling context manages a collection of workers that can
  30. be memorized using different data structures. Thus, a generic
  31. structure is available in order to simplify the choice of its type.
  32. Only the list data structure is available but further data
  33. structures(like tree) implementations are foreseen.
  34. \var starpu_worker_collection::workerids
  35. The workerids managed by the collection
  36. \var starpu_worker_collection::nworkers
  37. The number of workers in the collection
  38. \var starpu_worker_collection::type
  39. The type of structure (currently ::STARPU_WORKER_LIST is the only one available)
  40. \var starpu_worker_collection::has_next
  41. Checks if there is another element in collection
  42. \var starpu_worker_collection::get_next
  43. return the next element in the collection
  44. \var starpu_worker_collection::add
  45. add a new element in the collection
  46. \var starpu_worker_collection::remove
  47. remove an element from the collection
  48. \var starpu_worker_collection::init
  49. Initialize the collection
  50. \var starpu_worker_collection::deinit
  51. Deinitialize the colection
  52. \var starpu_worker_collection::init_iterator
  53. Initialize the cursor if there is one
  54. \struct starpu_sched_ctx_performance_counters
  55. Performance counters used by the starpu to indicate the
  56. hypervisor how the application and the resources are executing.
  57. \ingroup API_Scheduling_Contexts
  58. \var starpu_sched_ctx_performance_counters::notify_idle_cycle
  59. Informs the hypervisor for how long a worker has been idle in the specified context
  60. \var starpu_sched_ctx_performance_counters::notify_idle_end
  61. Informs the hypervisor that after a period of idle, the worker has just executed a task in the specified context. The idle counter it though reset.
  62. \var starpu_sched_ctx_performance_counters::notify_pushed_task
  63. Notifies the hypervisor a task has been scheduled on the queue of the worker corresponding to the specified context
  64. \var starpu_sched_ctx_performance_counters::notify_poped_task
  65. Informs the hypervisor a task executing a specified number of instructions has been poped from the worker
  66. \var starpu_sched_ctx_performance_counters::notify_post_exec_hook
  67. Notifies the hypervisor a task has just been executed
  68. @name Scheduling Contexts Basic API
  69. \ingroup API_Scheduling_Contexts
  70. \fn unsigned starpu_sched_ctx_create(const char *policy_name, int *workerids_ctx, int nworkers_ctx, const char *sched_ctx_name)
  71. \ingroup API_Scheduling_Contexts
  72. This function creates a scheduling context which uses the scheduling
  73. policy \p policy_name and assigns the workers in \p workerids_ctx to
  74. execute the tasks submitted to it.
  75. The return value represents the identifier of the context that has
  76. just been created. It will be further used to indicate the context the
  77. tasks will be submitted to. The return value should be at most
  78. \ref STARPU_NMAX_SCHED_CTXS.
  79. \fn unsigned starpu_sched_ctx_create_inside_interval(const char *policy_name, const char *sched_name, int min_ncpus, int max_ncpus, int min_ngpus, int max_ngpus, unsigned allow_overlap)
  80. \ingroup API_Scheduling_Contexts
  81. Create a context indicating an approximate interval of resources
  82. \fn void starpu_sched_ctx_delete(unsigned sched_ctx_id)
  83. \ingroup API_Scheduling_Contexts
  84. Delete scheduling context \p sched_ctx_id and transfer remaining
  85. workers to the inheritor scheduling context.
  86. \fn void starpu_sched_ctx_add_workers(int *workerids_ctx, int nworkers_ctx, unsigned sched_ctx_id)
  87. \ingroup API_Scheduling_Contexts
  88. This function adds dynamically the workers in \p workerids_ctx to the
  89. context \p sched_ctx_id. The last argument cannot be greater than
  90. \ref STARPU_NMAX_SCHED_CTXS.
  91. \fn void starpu_sched_ctx_remove_workers(int *workerids_ctx, int nworkers_ctx, unsigned sched_ctx_id)
  92. \ingroup API_Scheduling_Contexts
  93. This function removes the workers in \p workerids_ctx from the context
  94. \p sched_ctx_id. The last argument cannot be greater than
  95. STARPU_NMAX_SCHED_CTXS.
  96. \fn void starpu_sched_ctx_set_inheritor(unsigned sched_ctx_id, unsigned inheritor)
  97. \ingroup API_Scheduling_Contexts
  98. Indicate which context whill inherit the resources of this context
  99. when he will be deleted.
  100. \fn void starpu_sched_ctx_set_context(unsigned *sched_ctx_id)
  101. \ingroup API_Scheduling_Contexts
  102. Set the scheduling context the subsequent tasks will be submitted to
  103. \fn unsigned starpu_sched_ctx_get_context(void)
  104. \ingroup API_Scheduling_Contexts
  105. Return the scheduling context the tasks are currently submitted to
  106. \fn void starpu_sched_ctx_stop_task_submission(void)
  107. \ingroup API_Scheduling_Contexts
  108. Stop submitting tasks from the empty context list until the next time
  109. the context has time to check the empty context list
  110. \fn void starpu_sched_ctx_finished_submit(unsigned sched_ctx_id);
  111. \ingroup API_Scheduling_Contexts
  112. Indicate starpu that the application finished submitting to this
  113. context in order to move the workers to the inheritor as soon as
  114. possible.
  115. \fn unsigned starpu_sched_ctx_get_nworkers(unsigned sched_ctx_id)
  116. \ingroup API_Scheduling_Contexts
  117. Return the number of workers managed by the specified contexts
  118. (Usually needed to verify if it manages any workers or if it should be
  119. blocked)
  120. \fn unsigned starpu_sched_ctx_get_nshared_workers(unsigned sched_ctx_id, unsigned sched_ctx_id2)
  121. \ingroup API_Scheduling_Contexts
  122. Return the number of workers shared by two contexts.
  123. \fn unsigned starpu_sched_ctx_contains_worker(int workerid, unsigned sched_ctx_id)
  124. \ingroup API_Scheduling_Contexts
  125. Return 1 if the worker belongs to the context and 0 otherwise
  126. \fn unsigned starpu_sched_ctx_overlapping_ctxs_on_worker(int workerid)
  127. \ingroup API_Scheduling_Contexts
  128. Check if a worker is shared between several contexts
  129. \fn unsigned starpu_sched_ctx_is_ctxs_turn(int workerid, unsigned sched_ctx_id)
  130. \ingroup API_Scheduling_Contexts
  131. Manage sharing of resources between contexts: checkOB which ctx has
  132. its turn to pop.
  133. \fn void starpu_sched_ctx_set_turn_to_other_ctx(int workerid, unsigned sched_ctx_id)
  134. \ingroup API_Scheduling_Contexts
  135. Manage sharing of resources between contexts: by default a round_robin
  136. strategy is executed but the user can interfere to tell which ctx has
  137. its turn to pop.
  138. \fn double starpu_sched_ctx_get_max_time_worker_on_ctx(void)
  139. \ingroup API_Scheduling_Contexts
  140. Time sharing a resources, indicate how long a worker has been active
  141. in the current sched_ctx.
  142. @name Scheduling Context Priorities
  143. \ingroup API_Scheduling_Contexts
  144. \def STARPU_MIN_PRIO
  145. \ingroup API_Scheduling_Contexts
  146. Provided for legacy reasons.
  147. \def STARPU_MAX_PRIO
  148. \ingroup API_Scheduling_Contexts
  149. Provided for legacy reasons.
  150. \def STARPU_DEFAULT_PRIO
  151. \ingroup API_Scheduling_Contexts
  152. By convention, the default priority level should be 0 so that we can
  153. statically allocate tasks with a default priority.
  154. \fn int starpu_sched_ctx_set_min_priority(unsigned sched_ctx_id, int min_prio)
  155. \ingroup API_Scheduling_Contexts
  156. Defines the minimum task priority level supported by the scheduling
  157. policy of the given scheduler context. The default minimum priority
  158. level is the same as the default priority level which is 0 by
  159. convention. The application may access that value by calling the function
  160. starpu_sched_ctx_get_min_priority(). This function should only
  161. be called from the initialization method of the scheduling policy, and
  162. should not be used directly from the application.
  163. \fn int starpu_sched_ctx_set_max_priority(unsigned sched_ctx_id, int max_prio)
  164. \ingroup API_Scheduling_Contexts
  165. Defines the maximum priority level supported by the scheduling policy
  166. of the given scheduler context. The default maximum priority level is
  167. 1. The application may access that value by calling the
  168. starpu_sched_ctx_get_max_priority function. This function should only
  169. be called from the initialization method of the scheduling policy, and
  170. should not be used directly from the application.
  171. \fn int starpu_sched_ctx_get_min_priority(unsigned sched_ctx_id)
  172. \ingroup API_Scheduling_Contexts
  173. Returns the current minimum priority level supported by the scheduling
  174. policy of the given scheduler context.
  175. \fn int starpu_sched_ctx_get_max_priority(unsigned sched_ctx_id)
  176. \ingroup API_Scheduling_Contexts
  177. Returns the current maximum priority level supported by the scheduling
  178. policy of the given scheduler context.
  179. @name Scheduling Context Worker Collection
  180. \ingroup API_Scheduling_Contexts
  181. \fn struct starpu_worker_collection* starpu_sched_ctx_create_worker_collection(unsigned sched_ctx_id, enum starpu_worker_collection_type type)
  182. \ingroup API_Scheduling_Contexts
  183. Create a worker collection of the type indicated by the last parameter
  184. for the context specified through the first parameter.
  185. \fn void starpu_sched_ctx_delete_worker_collection(unsigned sched_ctx_id)
  186. \ingroup API_Scheduling_Contexts
  187. Delete the worker collection of the specified scheduling context
  188. \fn struct starpu_worker_collection* starpu_sched_ctx_get_worker_collection(unsigned sched_ctx_id)
  189. \ingroup API_Scheduling_Contexts
  190. Return the worker collection managed by the indicated context
  191. @name Scheduling Context Link with Hypervisor
  192. \ingroup API_Scheduling_Contexts
  193. \fn void starpu_sched_ctx_set_perf_counters(unsigned sched_ctx_id, struct starpu_sched_ctx_performance_counters *perf_counters)
  194. \ingroup API_Scheduling_Contexts
  195. Indicates to starpu the pointer to the performance counter
  196. \fn void starpu_sched_ctx_call_pushed_task_cb(int workerid, unsigned sched_ctx_id)
  197. \ingroup API_Scheduling_Contexts
  198. Callback that lets the scheduling policy tell the hypervisor that a
  199. task was pushed on a worker
  200. \fn void starpu_sched_ctx_notify_hypervisor_exists(void)
  201. \ingroup API_Scheduling_Contexts
  202. Allow the hypervisor to let starpu know he's initialised
  203. \fn unsigned starpu_sched_ctx_check_if_hypervisor_exists(void)
  204. \ingroup API_Scheduling_Contexts
  205. Ask starpu if he is informed if the hypervisor is initialised
  206. */