Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: Samy Chbinou <samy.chbinou@greenflops.com>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] StarPU
- Date: Wed, 25 Feb 2015 16:29:42 +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>
Hello,
Samy Chbinou, le Wed 25 Feb 2015 11:13:04 +0100, a écrit :
> 1/ Is it possible to choose the backend device that will do the work? ex
> CPU or
> GPU or both in parallel.
You can specify the STARPU_NCUDA=0 environment variable to prevent CUDA
workers from starting, and the same with CPUS using STARPU_NCPU=0
> 2/ In case it is in parallel, is it possible to trace (I tried with FxT
> wihtout
> success) the load for each Compute Unit?
You can use the STARPU_WORKER_STATS=1 environment variable to get a
summary, but FxT should have worked, please tell us what went wrong and
how.
> that is load in Mflops % on both CPU and GPU?
We haven't implemented counting Mflops for starpufft, that'd just be a
number of tasks.
> 3/ Can I integrate PAPI (for performance measurements)?
That has been on the TODO list for a long time, but it should feasible
to tinker something easily by adding PAPI initialization/destruction to
_starpu_cpu_worker().
Samuel
- [Starpu-devel] StarPU, Samy Chbinou, 25/02/2015
- Re: [Starpu-devel] StarPU, Samuel Thibault, 25/02/2015
Archives gérées par MHonArc 2.6.19+.