Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Problem with STARPU_PROLOGUE_CALLBACK_POP

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Problem with STARPU_PROLOGUE_CALLBACK_POP


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • To: Nathalie Furmento <nathalie.furmento@labri.fr>
  • Cc: "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] Problem with STARPU_PROLOGUE_CALLBACK_POP
  • Date: Thu, 17 Apr 2014 15:12:56 +0200
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>

Nathalie Furmento, le Thu 17 Apr 2014 13:10:43 +0200, a écrit :
> I realised that in examples/callback/prologue.c when modifying the call to
> starpu_task_insert() to have a NULL codelet, i.e
>
> int ret2 = starpu_task_insert(NULL,//&cl,
> //STARPU_RW, handle,
> STARPU_PROLOGUE_CALLBACK, prologue_callback_func,
> STARPU_PROLOGUE_CALLBACK_ARG, x,
> STARPU_PROLOGUE_CALLBACK_POP,
> pop_prologue_callback_func,
> STARPU_PROLOGUE_CALLBACK_POP_ARG, 5,
> 0);

Well, yes, we don't have to schedule tasks without a codelet, we
immediately terminate them. So those never get "popped" from the
scheduler.

Samuel





Archives gérées par MHonArc 2.6.19+.

Haut de le page