Objet : Developers list for StarPU
Archives de la liste
- From: Xavier Lacoste <xavier.lacoste@inria.fr>
- To: starpu-devel@lists.gforge.inria.fr
- Subject: [Starpu-devel] Accessing task in callback function
- Date: Mon, 24 Mar 2014 11:56:46 +0100
- 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,
Is there a way to access the runned task in a callback function ?
What I would like to do in my callback is to get profiling info from a task and then destroy it rather than keeping each task and postprocessing profiling.
But as far as I undestand I have the created task can't be an argument of the callback (as the task is not yet created when the arguments are defined), so is there an other way to access the task from the callback ?
XL.
----------------------------------------
Xavier Lacoste
INRIA Bordeaux Sud-Ouest
200, avenue de la Vieille Tour
33405 Talence Cedex
Tél : +33 (0)5 24 57 40 69
- [Starpu-devel] Accessing task in callback function, Xavier Lacoste, 24/03/2014
- Re: [Starpu-devel] Accessing task in callback function, Samuel Thibault, 24/03/2014
Archives gérées par MHonArc 2.6.19+.