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: Samuel Thibault <samuel.thibault@inria.fr>
  • To: Mathieu Faverge <mathieu.faverge@inria.fr>, starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Issue with lws
  • Date: Fri, 14 Sep 2018 18:15:36 +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>
  • Organization: I am not organized

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




Archives gérées par MHonArc 2.6.19+.

Haut de le page