Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] [Fwd: [Starpu-commits] r5299 - trunk/doc/chapters]

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] [Fwd: [Starpu-commits] r5299 - trunk/doc/chapters]


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • To: Nathalie Furmento <nathalie.furmento@labri.fr>, Cyril Roelandt <cyril.roelandt@inria.fr>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] [Fwd: [Starpu-commits] r5299 - trunk/doc/chapters]
  • Date: Thu, 26 Jan 2012 00:29:48 +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>

Nathalie Furmento, le Wed 25 Jan 2012 21:08:21 +0100, a écrit :
> I suppose it would make some sense to hide these fields along with the
> field magic into the field void* starpu_private ?

prev and next can be freely used by the schedulers. Moving them to the
job structure would make it very cumbersome. Moving the magic field
to the job structure would just lose the point that was made by its
introduction...

> What is starpu_private currently used for ?

The job pointer.

> The same thing should probably be done for the "per_worker_stats" field of
> the "starpu_codelet" structure. This would allow us to add fields for our
> convenience without modifying non-opaque types.
>
> Should we do that for -rc2 ?

I don't think it's work the potential bugs. Since it's not part of the
API that applications are supposed to use, we can move it later.

Samuel




  • Re: [Starpu-devel] [Fwd: [Starpu-commits] r5299 - trunk/doc/chapters], Samuel Thibault, 26/01/2012

Archives gérées par MHonArc 2.6.19+.

Haut de le page