Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Problem with starpu_mpi_wait_for_all and starpu_mpi_barrier functions

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Problem with starpu_mpi_wait_for_all and starpu_mpi_barrier functions


Chronologique Discussions 
  • From: Mirko Myllykoski <mirkom@cs.umu.se>
  • To: "COUTEYEN, Jean-marie" <jean-marie.couteyen-carpaye@airbus.com>
  • Cc: Starpu Devel <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] Problem with starpu_mpi_wait_for_all and starpu_mpi_barrier functions
  • Date: Fri, 09 Nov 2018 17:12:26 +0100
  • Authentication-results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=mirkom@cs.umu.se; spf=Pass smtp.mailfrom=mirkom@cs.umu.se; spf=None smtp.helo=postmaster@mail.cs.umu.se
  • Ironport-phdr: 9a23:ZTbi+hFqHkqPcKCjnegmmZ1GYnF86YWxBRYc798ds5kLTJ7zpc6wAkXT6L1XgUPTWs2DsrQY07WQ6/iocFdDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXdrXKo8DEdBAj0OxZrKeTpAI7SiNm82/yv95HJbAhEmDiwbaluIBmqsA7cqtQYjYx+J6gr1xDHuGFIe+NYxWNpIVKcgRPx7dqu8ZBg7ipdpesv+9ZPXqvmcas4S6dYDCk9PGAu+MLrrxjDQhCR6XYaT24bjwBHAwnB7BH9Q5fxri73vfdz1SWGIcH7S60/VC+85Kl3VhDnlCYHNyY48G7JjMxwkLlbqw+lqxBm3oLYfJ2ZOP94c6jAf90VWHBBU95eWCNdDY2yYYsBAfQcM+laoYnzpFQPohWlCAmwBu7vyCNEimPs0KEk1ekqDAHI3BYnH9ILqHnaq9T1NL0RUeCy0aLGyjXCb/dS2Tb964jIdQshofKNXbltdsfRzEgvFxnGjlWXrIzoJC+a1v8Xv2iG6upgSPiji3U5pAxopDWk28QiipHRi44IxF3I6T91zJg7KNC8UkJ2bsKoHIFOuyyaL4d6XN8uT311tCs/y7AJooK3cS0Ux5kiyBPTd/OKf5SN7x/mVeucIjF1j29/dr2lnRa9602gx/X8Vsaq1FZKqTJIktzWuXAM0xzf8NSISuBn8ke83DaPyhrf6vpaLkwslKrbLYAuwqIom5YOv0nPAjX6lFv4gaKSbEkp9fSk5/75brjmvpOcMpV7igD6MqQggMy/BuE4PxALX2ia4+S817rj/UjiTbpWlf06iLTZsJXHJcgBva62HRdZ0pw/5BanEzemzNMYkGEcLFJZYh2HlZDpO0zXLP/lE/i/nUqjkDNwyvDCP73hGYnNLmPZnLfuc7Z97FRcyAUtwtxF5pJUDKsBIPPpVUPrutzYFExxDwvhic3ANelQ5644HSqtD6afdabbq16FrKp7IeSFYsoQsSz8Jr4u4OPygG40nxoWdLOx1IoaQHm5BP57OAOSZn+60fkbFmJfmwskT+uirUyGVS9QYG2xXupo4zAhC4WjJYzYAJ2onfqa0XHoTdVtemlaBwXUQj/TfIKeVqJJMXrKe54zonk/TbGkDrQZ+1SrvQ7+xaBgK7ONqCYD84/myZ5u6r+KzE1gxXlPF82Yllq1YSRshGpRHm09x+ZipFE70VrRifEl0cwdLsRa4rZyail/NZPYyLUkWdX7WwaHdczPVVO7BM6rU2k8
  • 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>

Hi,

On 2018-11-09 14:07, COUTEYEN, Jean-marie wrote:

It is a race condition. The problem with "starpu_mpi_wait_for_all" is
not related to scheduling contexts.
(starpu_mpi.c:2051,starpu-1.2.6). The variables task and mpi may not
have the same value in different processes, resulting in a different
number of loops.

Ok. Thank you for the explanation.

(*) That function does not exist. Perhaps
"starpu_sched_ctx_set_context(0)" does that, I didn't check.

I have used starpu_sched_ctx_set_context(0) when I had to return back to the default scheduling context. It seems to work. Scheduling context numbering seems to begin from 1. The only weird thing is that the starpu_sched_ctx_get_context() function seems to return STARPU_NMAX_SCHED_CTXS when the default scheduling context is selected.

- Mirko




Archives gérées par MHonArc 2.6.19+.

Haut de le page