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: Fri, 17 Jan 2014 09:57:45 +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,

Here is a patch on trunk that add EXECUTE_ON_WORKER as parameter of starpu_task_build().

https://gist.github.com/XL64/8470303

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 à 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 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.

That can be useful, yes.

Samuel




Archives gérées par MHonArc 2.6.19+.

Haut de le page