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: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • Cc: Mathieu Faverge <Mathieu.Faverge@inria.fr>, starpu-devel@lists.gforge.inria.fr, Pierre Ramet <ramet@labri.fr>
  • Subject: Re: [Starpu-devel] starpu_mpi_insert_task() and profiling
  • Date: Tue, 10 Dec 2013 14:44:21 +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>


Le 10 déc. 2013 à 14:29, Samuel Thibault <samuel.thibault@ens-lyon.org> a
écrit :

> Xavier Lacoste, le Tue 10 Dec 2013 10:15:42 +0100, a écrit :
>> 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),
>
> This starts looking ugly :)
Indeed, I didn't know the task_build function :)
>
> It'd really be much more clean, and actually useful too, to have a build
> version of the MPI function.
>
> Samuel






Archives gérées par MHonArc 2.6.19+.

Haut de le page