Accéder au contenu.
Menu Sympa

starpu-devel - [Starpu-devel] Lifetime needed for a starpu_data_handle_t

Objet : Developers list for StarPU

Archives de la liste

[Starpu-devel] Lifetime needed for a starpu_data_handle_t


Chronologique Discussions 
  • From: Jean-Marie Couteyen <jean-marie.couteyen@inria.fr>
  • To: "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>
  • Subject: [Starpu-devel] Lifetime needed for a starpu_data_handle_t
  • Date: Tue, 09 Sep 2014 17:57:20 +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>

Hello,

I was wondering what was the lifetime needed for a starpu_data_handle_t. Must it be valid until all the task using it are finished or just until starpu_data_unregister_submit ?

In other word, is this kind of code valid :
"""
void function_inserting_tasks(double * tmp)
{
starpu_data_handle_t tmp_h;
starpu_variable_data_register(&tmp_h, 0, (uintptr_t)tmp, sizeof(double));
// Insert tasks using tmp_h.
starpu_data_unregister_submit(tmp_h);
}
"""
?

Because only registration functions take a pointer to a starpu_data_handle_t and other functions (task submission, unregistration,...) take directly the starpu_data_handle_t, I suspect the second hypothesis to be good, but I want to be sure... :)

Regards,

Jean-Marie




Archives gérées par MHonArc 2.6.19+.

Haut de le page