Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] StarPU can_execute hook with multiple implementations..

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] StarPU can_execute hook with multiple implementations..


Chronologique Discussions 
  • From: Cyril Roelandt <cyril.roelandt@inria.fr>
  • To: Usman Dastgeer <usman.dastgeer@liu.se>
  • Cc: "<starpu-devel@lists.gforge.inria.fr>" <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] StarPU can_execute hook with multiple implementations..
  • Date: Fri, 12 Oct 2012 15:43:50 +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>

On 10/11/2012 05:01 PM, Usman Dastgeer wrote:
I made the following fix. It works apparently. The only problem is that the
"can_execute" hook is often called>1 even though one worker is already found
to be eligible. I am using greedy scheduler. It's just a performance thing (multiple calls
etc.) but I guess its because all workers are simultaneously checking the pool for popping
task? So we can't do much about it?



We could cache the results of the calls to can_execute, but I'm not sure it would make a huge difference.

I pushed something similar yesterday. Thank you for reporting this issue.

WBR,
Cyril Roelandt.





Archives gérées par MHonArc 2.6.19+.

Haut de le page