Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: Andra Hugo <andra.hugo@inria.fr>
- Cc: starpu-devel@lists.gforge.inria.fr, Abdou Guermouche <abdou.guermouche@labri.fr>
- Subject: Re: [Starpu-devel] Sequential consistency and handles
- Date: Wed, 2 Apr 2014 18:52:49 +0200
- 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,
Andra Hugo, le Fri 28 Mar 2014 15:18:19 +0100, a écrit :
> We have a problem with the commit r12396. It seems that since this commit we
> are not allowed to unregister handles inside tasks or callbacks. For
> qr_mumps
> we do this all the time.
>
> What should we do to have a correct behavior? Currently it crashes inside an
> assert (data_interface.c: 621)
As discussed, unregistering is not safe within a task, because it has to
wait for pending transfers etc. starpu_unregister_submit should be used
instead. I have noted in my TODO list to add a callback variant.
Samuel
- Re: [Starpu-devel] Sequential consistency and handles, Samuel Thibault, 02/04/2014
Archives gérées par MHonArc 2.6.19+.