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: Cyril Bordage <cyril.bordage@inria.fr>
  • To: Samuel Thibault <samuel.thibault@ens-lyon.org>, 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 19:30:07 +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>

When I proposed this function, there was no link with my problem, but
juste to move forward the schmillblick.


Cyril.


Le 16/10/2013 18:50, Samuel Thibault a écrit :
> Cyril Bordage, le Thu 10 Oct 2013 21:48:36 +0200, a écrit :
>> I wrote a function named starpu_task_is_calibrated, maybe it can be
>> usefull http://codepad.org/5RhCFghq
>
> Well, it is not so usable, because we also need which case is not
> calibrated, to be able to force that one. Also, we can't strictly force
> the first worker or implementation which is not calibrated, we need to
> distribute over all cases which are not calibrated. Otherwise all the
> available non-calibrated tasks will go to the same worker with the same
> implementation.
>
> Samuel
>





Archives gérées par MHonArc 2.6.19+.

Haut de le page