Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Issue with lws

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Issue with lws


Chronologique Discussions 
  • From: Mathieu Faverge <mathieu.faverge@inria.fr>
  • To: Samuel Thibault <samuel.thibault@inria.fr>, starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Issue with lws
  • Date: Sat, 15 Sep 2018 14:46:29 +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>

Good Idea. I just did it, and indeed no more problem. I haven't tried with the new assertion yet, I'm using the 1.2.5 tarball.

Mathieu

Le 14/09/2018 à 18:15, Samuel Thibault a écrit :
Samuel Thibault, le ven. 14 sept. 2018 18:09:35 +0200, a ecrit:
Mathieu Faverge, le ven. 14 sept. 2018 11:13:45 +0200, a ecrit:
When I'm lucky, I got this assert:
simple: core/dependencies/implicit_data_deps.c:446:
_starpu_release_data_enforce_sequential_consistency: Assertion
`task_dependency_slot->task == task' failed.
This could look as if the same task gets executed twice, i.e. lws
wouldn't lock properly when stealing. I have added assertions on task
execution status in the 1.2 branch, could you try it?
To confirm that it's stealing which goes wrong, you could disable it by
making the select_victim() function in
src/sched_policies/locality_work_stealing_policy.c
just return -1;

Samuel



--
--
Mathieu Faverge
Maitre de conférence / Associate 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





Archives gérées par MHonArc 2.6.19+.

Haut de le page