Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] [Starpu-commits] [Review needed] Move $HOME/.starpu/sampling to $XDG_CACHE_HOME/starpu/sampling

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] [Starpu-commits] [Review needed] Move $HOME/.starpu/sampling to $XDG_CACHE_HOME/starpu/sampling


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • To: Cyril Roelandt <cyril.roelandt@inria.fr>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] [Starpu-commits] [Review needed] Move $HOME/.starpu/sampling to $XDG_CACHE_HOME/starpu/sampling
  • Date: Tue, 13 Dec 2011 19:41:18 +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>

Cyril Roelandt, le Tue 13 Dec 2011 17:33:11 +0100, a écrit :
> On 12/13/2011 05:06 PM, Ludovic Courtès wrote:
> >Nathalie Furmento<nathalie.furmento@labri.fr> skribis:
> >
> >>What about the recent commit which integrates STARPU_HOME?
> >
> >What is it used for?
>
> Isn't that the value passed to the --prefix option of the configure ?

No. See the code and documentation: I've just made it a replacement for
$HOME.

> Maybe what we should do is :
>
> 1) Check whether $HOME/.starpu/sampling exists, in which case we could store
> our perfmodels there.
> 2) Check whether $XDG_CACHE_HOME is defined : in this case, store the
> perfmodels in $XDG_CACHE_HOME/starpu/sampling
> 3) Store the perfmodels in $STARPU_HOME/starpu/sampling
>
> How good would that be ?

As I said in another mail, I'd rather have a straight algorithm: look
for a known list of places, and if none exists, create the first of
the list. The list only containing places which have the corresponding
variables being defined.

Samuel





Archives gérées par MHonArc 2.6.19+.

Haut de le page