Objet : Developers list for StarPU
Archives de la liste
- 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:55:28 +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>
Le 19 févr. 2013 à 23:17, Samuel Thibault a écrit :
> Xavier Lacoste, le Tue 19 Feb 2013 15:16:47 +0100, a écrit :
>> So the problem is that the CUDA worker keeps incrementing nready by
>> calling _starpu_push_task.
>>
>> Do you think there is something missing in my scheduler to solve that ?
>
> You should probably call _starpu_push_task_to_workers instead.
The problem is that i'm not the one calling it, I'm only calling API
available functions.
This call is in the CUDA driver code, when he pop a task which is not
executable on CUDA devices.
>
> Samuel
- Re: [Starpu-devel] hang with 8659, (suite)
- Re: [Starpu-devel] hang with 8659, Xavier Lacoste, 19/02/2013
- Re: [Starpu-devel] hang with 8659, Xavier Lacoste, 19/02/2013
- Re: [Starpu-devel] hang with 8659, Samuel Thibault, 19/02/2013
- Re: [Starpu-devel] hang with 8659, Xavier Lacoste, 20/02/2013
- Re: [Starpu-devel] hang with 8659, Samuel Thibault, 20/02/2013
- Re: [Starpu-devel] hang with 8659, Xavier Lacoste, 20/02/2013
- Re: [Starpu-devel] hang with 8659, Samuel Thibault, 22/02/2013
- Re: [Starpu-devel] hang with 8659, Samuel Thibault, 22/02/2013
- Re: [Starpu-devel] hang with 8659, Xavier Lacoste, 23/02/2013
- Re: [Starpu-devel] hang with 8659, Samuel Thibault, 19/02/2013
- Re: [Starpu-devel] hang with 8659, Xavier Lacoste, 20/02/2013
- Re: [Starpu-devel] Assert fail with 8659, Andra Hugo, 15/02/2013
Archives gérées par MHonArc 2.6.19+.