Objet : Developers list for StarPU
Archives de la liste
- From: Mathieu Faverge <mathieu.faverge@inria.fr>
- To: starpu-devel@lists.gforge.inria.fr
- Cc: Gregoire Pichon <gregoire.pichon@inria.fr>
- Subject: [Starpu-devel] Task naming in traces
- Date: Mon, 7 Dec 2015 17:58:25 +0300
- 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,
We have discover that in the StarPU 1.2.0rc4 version, the trace don't take into account the codelet name in the trace generation, but return only insert_tasks function.
We had to add the field STARPU_NAME in the starpu_insert_task functions. Is that really necessary ? or is it a bug ?
Because it seems more costly to do it this way, and it replicates information you already gave in the codelet fields. I understandthat you might want to overload it, but I don't get why you don't use anymore the codelet name as a default :).
Best,
Mathieu
--
--
Mathieu Faverge
Maitre de conférence / Assistant Professor
Institut Polytechnique de Bordeaux - ENSEIRB-Matmeca
INRIA Bordeaux - Sud-Ouest, HiePACS Team
200 avenue de la vielle tour
33405 Talence Cedex
Phone: (+33) 5 24 57 40 73
- [Starpu-devel] Task naming in traces, Mathieu Faverge, 07/12/2015
- Re: [Starpu-devel] Task naming in traces, Samuel Thibault, 07/12/2015
- Re: [Starpu-devel] Task naming in traces, Mathieu Faverge, 07/12/2015
- Re: [Starpu-devel] Task naming in traces, Samuel Thibault, 07/12/2015
- Re: [Starpu-devel] Task naming in traces, Mathieu Faverge, 07/12/2015
- Re: [Starpu-devel] Task naming in traces, Samuel Thibault, 07/12/2015
Archives gérées par MHonArc 2.6.19+.