Accéder au contenu.
Menu Sympa

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

Objet : Developers list for StarPU

Archives de la liste

Re: [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: Re: [Starpu-devel] starpu_mpi_insert_task() and profiling
  • Date: Tue, 10 Dec 2013 10:15:36 +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>

For the execute_on_worker issue, I'll add a 

#define STARPU_EXECUTE_ON_WORKER (15<<16)  

And create a patch modifying starpu_mpi_insert_task.c / starpu_insert_task_util.c that i'll send you.
STARPU_EXECUTE_ON_WORKER, workerid, would set workerid and execute_on_a_specific_worker except if workerid is -1.

I have to modify my code to validate my changes before sending the patch.

For the profiling issue maybe I could do an other patch adding #define STARPU_TASKPTR (16<<16)  which would trigger task->destroy=0 and copy task pointer to the given address.
That would give STARPU_TASKPTR, (struct starpu_task **) &(taskptr),

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








Le 10 déc. 2013 à 09:21, Xavier Lacoste <xavier.lacoste@inria.fr> a écrit :

Hello,

An other question about starpu_mpi_insert_task() :
Is it possible to set the execute_on_a_specific_worker / workerid via starpu_mpi_insert_task() ?

Regards,

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








Le 9 déc. 2013 à 17:32, Xavier Lacoste <xavier.lacoste@inria.fr> a écrit :

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