Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: Miguel Palhas <mpalhas@gmail.com>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] pheft problem?
- Date: Tue, 5 Nov 2013 15:02:55 +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>
Hello,
It seems nobody had a look at this issue.
Miguel Palhas, le Tue 13 Aug 2013 09:32:27 +0200, a écrit :
> When using pheft on my algorithm, i have a problem with a specific task,
> which hangs the scheduler as soon as it's sampling information has 10
> executions
>
> This only happens when i set the codelet for that task to use only
> STARPU_CUDA
> (while it depends on data that is ALWAYS executed on a CPU task)
> Is this a bug with the pheft scheduler?
Possibly. I have however just added a testcase
(tests/parallel_tasks/cuda_only), it does finish fine. How are you
specifying CUDA only, through where or through can_execute? (the latter
was buggued for pheft, I have just fixed it).
Could you take a gdb thread apply all bt trace, so we get an idea of
what it is stuck on?
Samuel
- Re: [Starpu-devel] pheft problem?, Samuel Thibault, 05/11/2013
- Re: [Starpu-devel] pheft problem?, Miguel Palhas, 05/11/2013
- Re: [Starpu-devel] pheft problem?, Samuel Thibault, 06/11/2013
- Re: [Starpu-devel] pheft problem?, Miguel Palhas, 05/11/2013
Archives gérées par MHonArc 2.6.19+.