Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] StarPU : impossible de compiler avec SimGrid, MPI et Fxt sur PlaFRIM

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] StarPU : impossible de compiler avec SimGrid, MPI et Fxt sur PlaFRIM


Chronologique Discussions 
  • From: Emmanuel Agullo <emmanuel.agullo@inria.fr>
  • To: Ludovic Courtes <ludovic.courtes@inria.fr>
  • Cc: starpu-devel <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] StarPU : impossible de compiler avec SimGrid, MPI et Fxt sur PlaFRIM
  • Date: Thu, 27 Aug 2020 11:23:26 +0200 (CEST)
  • 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,

Thanks Florent for the suggestion.

> Carrément, ou simplement rajouter fxt à « starpu-simgrid » si c’est pas
> utile d’avoir les deux variantes.

Good idea, Ludo. Indeed, in the starpu-simgrid case, the fxt overhead is much
less critical than in the actual starpu case, and it might not be worth
maintaining two separate guix packages.

Maybe the only point is to make sure the user is aware that fxt is around so
that he / she thinks to play with the STARPU_FXT_TRACE environment variable
( https://files.inria.fr/starpu/doc/html/OfflinePerformanceTools.html )
in order to disable them at runtime. One way to make sure the user is aware
of that is to name the (guix) package accordingly, for instance
starpu-simgrid-fxt . This would be consistent with the starpu-fxt package
naming. (And there would not be a starpu-simgrid (guix) package anymore.)

Best regards,

Manu




Archives gérées par MHonArc 2.6.19+.

Haut de le page