Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] MPI scaling

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] MPI scaling


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • To: Xavier Lacoste <xavier.lacoste@inria.fr>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] MPI scaling
  • Date: Tue, 24 Jun 2014 17:22:57 +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>

Xavier Lacoste, le Tue 24 Jun 2014 15:29:10 +0200, a écrit :
> I don't see it in starpu 1.1.2, is it new in 1.2 ? Is it different from ws ?

Ah, I perhaps didn't backport it to 1.1.2 indeed, probably due to needed
changes in the StarPU core.

It is different from ws in that it tries to preserve locality. It may
not make a difference on 8 cores, though.

> I already tried using eager and giving non zero priority to these
> update tasks (as I saw in online documentation that the non zero
> priority tasks are put in front of the queue). Is this different from
> prio scheduler behaviour ?

Ah, yes, eager does support binary priorities indeed :)

The behavior will be the same with prio, except that prio preserves the
task release order, while eager would push them in a FIFO order. That
may make a difference depending on whether it's important for your
prioritized tasks.

Samuel




Archives gérées par MHonArc 2.6.19+.

Haut de le page