Objet : Developers list for StarPU
Archives de la liste
Re: [Starpu-devel] Could STARPU_COMMUTE change order with a single worker ?
Chronologique Discussions
- From: Samuel Thibault <samuel.thibault@inria.fr>
- To: Jerome Robert <jeromerobert@gmx.com>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] Could STARPU_COMMUTE change order with a single worker ?
- Date: Thu, 16 Feb 2017 14:09:51 +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>
- Organization: I am not organized
Hello,
Jerome Robert, on jeu. 16 févr. 2017 12:04:11 +0100, wrote:
> With multiple worker, inserting T1 then T2, with both allowed to commute
> (STARPU_COMMUTE flag), could lead to and execution order of T1-T2 or T2-T1.
> But with only one worker (STARPU_NCPU=1), does the current implementation
> will always execute T1-T2 (same as insertion order) or could they be
> reordered ?
There is nothing that prevents a reordering, but in practice they
will probably be always in order: I guess in your case they are
immediately ready for execution? In that case the dependency stages in
_starpu_enforce_deps_and_schedule() return immediately, and the task is
thus pushed to the scheduler from the starpu_task_submit() call, and
thus before starpu_task_submit returns. Then it's up to the scheduler of
course, but they usually keep the tasks in submission order. In the case
of prio, two tasks with the same priority seem to be kept in order.
Samuel
- [Starpu-devel] Could STARPU_COMMUTE change order with a single worker ?, Jerome Robert, 16/02/2017
- Re: [Starpu-devel] Could STARPU_COMMUTE change order with a single worker ?, Samuel Thibault, 16/02/2017
Archives gérées par MHonArc 2.6.19+.