Objet : Developers list for StarPU
Archives de la liste
- 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] initialised SCRATCH buffer
- Date: Thu, 5 Jan 2012 13:17:14 +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>
Xavier Lacoste, le Thu 05 Jan 2012 11:10:49 +0100, a écrit :
> Yes this is what I mean this array depends on parameters of the task.
> It is build from the bloc number and the whole sparse matrix structure which
> are given through cl->args.
> The bloc number is on the computing device but the sparse matrix is just a
> pointer to the data and the GPU can't see what is pointed to as it is not
> copied.
>
> Yes I could build the array in my codelet using my cl->args, then send it to
> the GPU.
So you mean that initialization can only be performed on a CPU? Isn't it
possible you create a task just for it? That will declare the CPU-only
computation time, and still let StarPU perform the transfer as it sees
fit.
Samuel
- [Starpu-devel] initialised SCRATCH buffer, Xavier Lacoste, 05/01/2012
- <Suite(s) possible(s)>
- Re: [Starpu-devel] initialised SCRATCH buffer, Samuel Thibault, 05/01/2012
- Re: [Starpu-devel] initialised SCRATCH buffer, Xavier Lacoste, 05/01/2012
- Message indisponible
- Re: [Starpu-devel] initialised SCRATCH buffer, Samuel Thibault, 05/01/2012
- Re: [Starpu-devel] initialised SCRATCH buffer, Xavier Lacoste, 05/01/2012
- Re: [Starpu-devel] initialised SCRATCH buffer, Samuel Thibault, 05/01/2012
Archives gérées par MHonArc 2.6.19+.