Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: Berenger Bramas <berenger.bramas@inria.fr>
- Cc: Emmanuel Agullo <emmanuel.agullo@inria.fr>, starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] CUDA Allocate problem
- Date: Tue, 26 Mar 2013 12:55:30 +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>
Berenger Bramas, le Tue 26 Mar 2013 12:50:12 +0100, a écrit :
> "oops in allocate_vector_buffer_on_node (datawizard/interfaces/
> vector_interface.c:264)... 4: unspecified launch failure"
Interesting error from CUDA...
It looks like we can not really rely in CUDA to be able to tell
us when it does not have memory any more... You can try to set
STARPU_LIMIT_CUDA_MEM to the amount of MiB you want to let StarPU use
before making room without waiting for CUDA to report errors.
Samuel
- [Starpu-devel] CUDA Allocate problem, Berenger Bramas, 26/03/2013
- Re: [Starpu-devel] CUDA Allocate problem, Samuel Thibault, 26/03/2013
- Re: [Starpu-devel] CUDA Allocate problem, Berenger Bramas, 26/03/2013
- Re: [Starpu-devel] CUDA Allocate problem, Samuel Thibault, 26/03/2013
- Re: [Starpu-devel] CUDA Allocate problem, Berenger Bramas, 26/03/2013
- Re: [Starpu-devel] CUDA Allocate problem, Samuel Thibault, 26/03/2013
Archives gérées par MHonArc 2.6.19+.