Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@inria.fr>
- To: Maxim Abalenkov <maxim.abalenkov@gmail.com>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] [trace interpretation]
- Date: Mon, 6 Aug 2018 17:23:13 +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,
Just for information, I don't work on scheduling contexts, so I only
provide the ideas I happen to have on this.
Maxim Abalenkov, le mar. 31 juil. 2018 16:20:53 +0100, a ecrit:
> 1) create two contexts (i) for part a and (ii) for parts b and c.
> 2) launch context (i) and (ii) simultaneously and let them perform their
> tasks
> 3) once context (i) has finished merge it with context (ii)
> 4) re-create context (i) for the subsequent panel
>
> Maybe it is not optimal and I shouldn’t merge at all?
I don't know. Contexts are quite heavy indeed, so perhaps you should
just keep them, and just resize them as seems to be needed.
Samuel
- Re: [Starpu-devel] [trace interpretation], Maxim Abalenkov, 06/08/2018
- Re: [Starpu-devel] [trace interpretation], Samuel Thibault, 06/08/2018
- <Suite(s) possible(s)>
- Re: [Starpu-devel] [trace interpretation], Samuel Thibault, 06/08/2018
Archives gérées par MHonArc 2.6.19+.