Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Incoherence between starpu_mpi_init and starpu_mpi_init_conf

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Incoherence between starpu_mpi_init and starpu_mpi_init_conf


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@inria.fr>
  • To: Philippe SWARTVAGHER <philippe.swartvagher@inria.fr>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Incoherence between starpu_mpi_init and starpu_mpi_init_conf
  • Date: Wed, 12 Feb 2020 05:00:54 -0800
  • 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>
  • Organization: I am not organized

Hello,

Philippe SWARTVAGHER, le mer. 12 févr. 2020 13:52:20 +0100, a ecrit:
> Anyway, is it normal that starpu_mpi_init() doesn't make all the staff of
> starpu_mpi_init_conf(): backend initialization and core reservation ?
> Calling starpu_init() and then starpu_mpi_init() seems to be allowed by the
> doc, but starpu_mpi_init() should also initialize backend and eventually
> reserve core IMHO.
>
> Is it a bug ?

No, it is the original semantic of starpu_mpi_init(). Initially you had
to call starpu_init() then starpu_mpi_init(). We added
starpu_mpi_init_conf() as a helper to do both. Perhaps the doc could be
reworded to make it clearer.

Samuel




Archives gérées par MHonArc 2.6.19+.

Haut de le page