Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] activity.data : nsubmitted, nready

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] activity.data : nsubmitted, nready


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • To: Jean-Marie Couteyen <jean-marie.couteyen@inria.fr>
  • Cc: "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] activity.data : nsubmitted, nready
  • Date: Mon, 17 Nov 2014 11:18:13 +0100
  • 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>

Jean-Marie Couteyen, le Fri 14 Nov 2014 19:02:03 +0100, a écrit :
> The number of tasks left at the end of my executions is exactly the
> difference between number of calls of "_starpu_push_task" and
> "starpu_push_task_to_workers". (starpu_push_task is the only caller of
> starpu_push_task_to_workers, at least in my executions.)
>
> I suppose _STARPU_TRACE_JOB_PUSH macro should be used inside
> "starpu_push_task_to_workers" instead of "_starpu_push_task".

Ah, right, for tasks with a NULL codelet that makes a difference. Also,
the other callers of starpu_push_task_to_workers will have called pop,
so it makes sense to push again.

Samuel




Archives gérées par MHonArc 2.6.19+.

Haut de le page