>>
>>> It is documented in
>>> http://developer.download.nvidia.com/compute/cuda/4_0/docs/GPUDirect_Technology_Overview.pdf
>>> set CUDA_NIC_INTEROP=1
>>>
>>>
>>> From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On
.@open-mpi.org [mailto:devel-boun...@open-mpi.org] On
> > Behalf Of Sebastian Rinke
> > Sent: Wednesday, January 18, 2012 8:15 AM
> > To: Open MPI Developers
> > Subject: Re: [OMPI devel] GPUDirect v1 issues
> >
> > Setting the environment variable f
Rinke
Sent: Friday, January 20, 2012 12:21 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] GPUDirect v1 issues
With
* MLNX OFED stack tailored for GPUDirect
* RHEL + kernel patch
* MVAPICH2
it is possible to monitor GPUDirect v1 activities by means of observing changes
to values in
* /sys
> set CUDA_NIC_INTEROP=1
>
>
> From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On
> Behalf Of Sebastian Rinke
> Sent: Wednesday, January 18, 2012 8:15 AM
> To: Open MPI Developers
> Subject: Re: [OMPI devel] GPUDirect v1 issues
>
> Settin
Developers
Subject: Re: [OMPI devel] GPUDirect v1 issues
Setting the environment variable fixed the problem for Open MPI with CUDA
4.0. Thanks!
However, I'm wondering why this is not documented in the NVIDIA GPUDirect
package.
Sebastian.
On Jan 18, 2012, at 1:28 AM, Rolf vandeVaart
o longer necessary.
>
> Rolf
>
>
> From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On
> Behalf Of Sebastian Rinke
> Sent: Tuesday, January 17, 2012 5:22 PM
> To: Open MPI Developers
> Subject: Re: [OMPI devel] GPUDirect v1 issues
>
> Th
Yes, the step outlined in your second bullet is no longer necessary.
Rolf
From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On Behalf
Of Sebastian Rinke
Sent: Tuesday, January 17, 2012 5:22 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] GPUDirect v1 issues
Thank you
pen-mpi.org [mailto:devel-boun...@open-mpi.org]
On Behalf Of Sebastian Rinke
Sent: Tuesday, January 17, 2012 12:08 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] GPUDirect v1 issues
I use CUDA 4.0 with MVAPICH2 1.5.1p1 and Open MPI 1.4.2.
Attached you find a little test case which is based on
age-
>From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org]
>On Behalf Of Sebastian Rinke
>Sent: Tuesday, January 17, 2012 12:08 PM
>To: Open MPI Developers
>Subject: Re: [OMPI devel] GPUDirect v1 issues
>
>I use CUDA 4.0 with MVAPICH2 1.5.1p1 and Open MPI 1.4.2
t;
> Ken
> -Original Message-
> From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On
> Behalf Of Rolf vandeVaart
> Sent: Tuesday, January 17, 2012 7:54 AM
> To: Open MPI Developers
> Subject: Re: [OMPI devel] GPUDirect v1 issues
>
> I am not aware
pi.org] On
Behalf Of Rolf vandeVaart
Sent: Tuesday, January 17, 2012 7:54 AM
To: Open MPI Developers
Subject: Re: [OMPI devel] GPUDirect v1 issues
I am not aware of any issues. Can you send me a test program and I can try
it out?
Which version of CUDA are you using?
Rolf
>-Original Messa
I am not aware of any issues. Can you send me a test program and I can try it
out?
Which version of CUDA are you using?
Rolf
>-Original Message-
>From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org]
>On Behalf Of Sebastian Rinke
>Sent: Tuesday, January 17, 2012 8:50 AM
>
12 matches
Mail list logo
