Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Problem with prio and tasks with several implementations

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Problem with prio and tasks with several implementations


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • To: Cyril Bordage <cyril.bordage@inria.fr>
  • Cc: starpu-devel <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] Problem with prio and tasks with several implementations
  • Date: Wed, 16 Oct 2013 18:48:40 +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>

Cyril Bordage, le Thu 10 Oct 2013 20:35:36 +0200, a écrit :
> In _starpu_priority_pop_task, there is a loop over the implementations,
> but no break when a worker is choosen. I think a break is missing.

Ah, right, fixed it.

> In my application, I need to do a calibration step. You've guided me to
> the prio policy. But, prio cannot consider the model at all. So when I
> have several implementations, the first is always choosen and my task
> still remains uncalibrated. Is it not a good point, that prio policy
> chooses the best implementation (or an uncalibrated implementation) ?

It is. The idea would be more or less doing the same as in dmda, indeed.
Just nobody took the time to make prio do it (and I didn't know you had
several implementations for the same codelet).

Samuel





Archives gérées par MHonArc 2.6.19+.

Haut de le page