Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] hang with 8659

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] hang with 8659


Chronologique Discussions 
  • From: Xavier Lacoste <xavier.lacoste@inria.fr>
  • To: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] hang with 8659
  • Date: Wed, 20 Feb 2013 08:57:59 +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>

Then maybe :

_starpu_push_task(); nready++
_starpu_handle_job_termination(); nready--
_starpu_cuda_driver_once(); if task cannot be executed localy, after push,
nready--;

XL.

Le 19 févr. 2013 à 23:10, Samuel Thibault a écrit :

> Xavier Lacoste, le Tue 19 Feb 2013 15:34:50 +0100, a écrit :
>> If I understand well StarPU code shouldn't it be the _starpu_pop_task
>> which decrement nready counter ?
>>
>> Maybe it could be done like that ?
>>
>> _starpu_push_task() increment nready
>> _starpu_pop_task() decrement nready
>
> Well, no, because then starpu_shutdown() would kill workers as soon as
> all tasks are popped into the scheduling policy, and not wait for their
> completion.
>
>> _starpu_cuda_driver_once() increment if task can be executed localy
>> _starpu_handle_job_termination() decrement nready
>
> Samuel






Archives gérées par MHonArc 2.6.19+.

Haut de le page