Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Problem with CUDA 4.0

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Problem with CUDA 4.0


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • To: Lu Li <luli757@student.liu.se>, starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Problem with CUDA 4.0
  • Date: Tue, 23 Aug 2011 12:43:07 +0200
  • 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>

Samuel Thibault, le Thu 11 Aug 2011 00:47:04 +0200, a écrit :
> Lu Li, le Wed 10 Aug 2011 09:20:00 +0200, a écrit :
> > I upgrade cuda to 4.0. then previously well-tested examples execute
> > with run-time error: "main: datawizard/copy_driver.c:116:
> > copy_data_1_to_1_generic: Assertion `cures == cudaSuccess' failed."
> >
> > Anyone have ideas how to solve this problem?
>
> Is this perhaps a NUMA machine?
>
> As a workaround, you can set HAVE_CUDA_MEMCPY_PEER to 0 in
> ./src/common/config.h *after* ./configure, but you will lose GPU-GPU
> direct transfers capability.

Nathalie added a --disable-cuda-memcpy-peer option to ./configure, to do
the same more easily.

Samuel





Archives gérées par MHonArc 2.6.19+.

Haut de le page