Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@inria.fr>
- To: FLINT Clément (ETU MAI) <clement.flint@etu.unistra.fr>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] Question regarding StarPU's coherency model
- Date: Fri, 22 May 2020 21:19:03 +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>
- Organization: I am not organized
Hello,
FLINT Clément (ETU MAI), le ven. 22 mai 2020 10:59:10 +0200, a ecrit:
> In order to implement good heuristics, we need to have access to tasks
> successors and predecessors.
> When a ready task is pushed to the scheduler, we would want to compute a
> score
> based on this task's successors's predecessors (which may or may not be
> ready).
> Is there any standard way to get this information in starpu ?
Not by default, because there are various ways for a task to get
activated etc, so do not try to look for just one way.
The simplest supported way is to enable graph recording, see for
instance graph_test_policy.c which uses it. Basically you set
_starpu_graph_record to 1, and then you can use the _starpu_graph_*
functions.
Samuel
- [Starpu-devel] Question regarding StarPU's coherency model, ETU MAI, 22/05/2020
- Re: [Starpu-devel] Question regarding StarPU's coherency model, Samuel Thibault, 22/05/2020
Archives gérées par MHonArc 2.6.19+.