Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Assert failure with regenerate flag enabled

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Assert failure with regenerate flag enabled


Chronologique Discussions 
  • From: Jeff Hand <jeffrey.hand@gmail.com>
  • To: Samuel Thibault <samuel.thibault@ens-lyon.org>, Starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Assert failure with regenerate flag enabled
  • Date: Wed, 19 Nov 2014 10:22:51 -0600
  • 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>

On Wed, Nov 19, 2014 at 4:54 AM, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
Jeff Hand, le Tue 18 Nov 2014 09:45:59 -0600, a écrit :
> On a slightly different topic, I'm wondering: How can dependencies be changed?

> I'm not aware of a way change or clear the dependencies.

We haven't really thought about an interface for this.

With the chain A->B->C->D, it will likely be a long term requirement to change to A->C->B->D quickly. 

Why was I using dependencies in the first place?
1. make D dependant on A rather than the previous task (priming the pipeline)
2. declaring the dependency of a task output routed to multiple task inputs

Is the solution to enable data consistency and have the callback submit the next task in the pipeline?

Can I guarantee the dependencies of the output to many inputs occurs?  Would it require a StarPU pause, submit the many tasks, and resume StarPU?




Archives gérées par MHonArc 2.6.19+.

Haut de le page