Accéder au contenu.
Menu Sympa

starpu-devel - [Starpu-devel] starpu_mpi_insert_task() and profiling

Objet : Developers list for StarPU

Archives de la liste

[Starpu-devel] starpu_mpi_insert_task() and profiling


Chronologique Discussions 
  • From: Xavier Lacoste <xavier.lacoste@inria.fr>
  • To: starpu-devel@lists.gforge.inria.fr
  • Cc: Mathieu Faverge <Mathieu.Faverge@inria.fr>, Pierre Ramet <ramet@labri.fr>
  • Subject: [Starpu-devel] starpu_mpi_insert_task() and profiling
  • Date: Mon, 9 Dec 2013 17:32:53 +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,

I'm thinking of modifying PaStiX + StarPU source code so that it works with MPI.

As I understand the more convenient way is to use starpu_mpi_insert_task() which will handle all the required communication between nodes.

But if I go from the starpu_task_submit() model to the insert_task model, I cannot get profilling info from my tasks after execution as I have no struct starpu_task anymore.
(I print my profiling info as done in examples/profiling/profiling.c)

Is there a way to use the starpu_mpi_insert_task(), tell StarPU to set the destroy field to 0, and get the generated task to be able to do retrieve some profiling info from it ?
Maybe I could do it through a callback function but wouldn't this increase the computational time before starpu_wait_for_all() returns ?

Have a nice day,

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











Archives gérées par MHonArc 2.6.19+.

Haut de le page