MATLAB + CULA Dense 14 on Windows 7 challenges
2 posts
• Page 1 of 1
MATLAB + CULA Dense 14 on Windows 7 challenges
Folks --
I'm trying to use the CULA link framework to call CULA blas and lapack routines from MATLAB. Following are some of the specs I have:
CULA version: Dense, R14
MATLAB version: R2011a
OS: Windows 7 x64
CUDA driver version: 4.1
According to one of the previous blog posts, I am uainf a .bat file to load MATLAB, where the content of the bat file are as follows:
%%%%%%%%
SET LAPACK_VERSION=cula_lapack_link.dll
SET BLAS_VERSION=cula_lapack_link.dll
SET LAPACK_VERBOSITY=1
if "%PROCESSOR_ARCHITECTURE%" == "AMD64" set CULA_ILP64=1
set CULA_DEBUG_LOG=%USERPROFILE%\matlab_cula.log
set filename=%~f0
for %%F in ("%filename%") do set THISDIR=%%~dpF
"%THISDIR%matlab.exe"
%%%%%%%%%%%
I have the CULA bin path (C:\Program Files\CULA\R14\bin64) set in my system path.
However, when I load up my MATLAB using the above .bat file, and try the following command:
A = rand(1500,1500,'single');
tic; [u s v] = svd(A); toc
I get the following message:
cpu_id: x86 Family 6 Model 12 Stepping 2, GenuineIntel
libmwlapack: trying environment...
libmwlapack: loading cula_lapack_link.dll
libmwlapack: loaded cula_lapack_link.dll@000000003E640000
libmwlapack: cula_lapack_link.dll is not a compatibility layer.
The log file shows the following:
cula info: sgesvd (N, N, 1500, 1500, 0000000004FC0040, 1500, 000000003CC88AC0, 0000000000000000, 1500, 0000000000000000, 1500)
cula info: issuing to GPU (over threshold)
cula info: done
cula info: sgesvd (N, N, 1500, 1500, 0000000004FC0040, 1500, 000000003CC8A240, 0000000000000000, 1500, 0000000000000000, 1500)
cula info: issuing to CPU (work query)
cula info: work query returned 52500
cula info: done
I think that MATALB is not able to load/use the CULA version of BLAS/LAPACK, and therefore falls back on its native libraries.
Could anyone please advise me as to why I am being unable to call the CULA version of svd?
Many thanks!
I'm trying to use the CULA link framework to call CULA blas and lapack routines from MATLAB. Following are some of the specs I have:
CULA version: Dense, R14
MATLAB version: R2011a
OS: Windows 7 x64
CUDA driver version: 4.1
According to one of the previous blog posts, I am uainf a .bat file to load MATLAB, where the content of the bat file are as follows:
%%%%%%%%
SET LAPACK_VERSION=cula_lapack_link.dll
SET BLAS_VERSION=cula_lapack_link.dll
SET LAPACK_VERBOSITY=1
if "%PROCESSOR_ARCHITECTURE%" == "AMD64" set CULA_ILP64=1
set CULA_DEBUG_LOG=%USERPROFILE%\matlab_cula.log
set filename=%~f0
for %%F in ("%filename%") do set THISDIR=%%~dpF
"%THISDIR%matlab.exe"
%%%%%%%%%%%
I have the CULA bin path (C:\Program Files\CULA\R14\bin64) set in my system path.
However, when I load up my MATLAB using the above .bat file, and try the following command:
A = rand(1500,1500,'single');
tic; [u s v] = svd(A); toc
I get the following message:
cpu_id: x86 Family 6 Model 12 Stepping 2, GenuineIntel
libmwlapack: trying environment...
libmwlapack: loading cula_lapack_link.dll
libmwlapack: loaded cula_lapack_link.dll@000000003E640000
libmwlapack: cula_lapack_link.dll is not a compatibility layer.
The log file shows the following:
cula info: sgesvd (N, N, 1500, 1500, 0000000004FC0040, 1500, 000000003CC88AC0, 0000000000000000, 1500, 0000000000000000, 1500)
cula info: issuing to GPU (over threshold)
cula info: done
cula info: sgesvd (N, N, 1500, 1500, 0000000004FC0040, 1500, 000000003CC8A240, 0000000000000000, 1500, 0000000000000000, 1500)
cula info: issuing to CPU (work query)
cula info: work query returned 52500
cula info: done
I think that MATALB is not able to load/use the CULA version of BLAS/LAPACK, and therefore falls back on its native libraries.
Could anyone please advise me as to why I am being unable to call the CULA version of svd?
Many thanks!
- raffayhamid
- Posts: 1
- Joined: Wed Mar 28, 2012 11:28 am
Re: MATLAB + CULA Dense 14 on Windows 7 challenges
You can safely ignore the messages produced by Matlab ("libmwlapack: cula_lapack_link.dll is not a compatibility layer."). The logfile indicates that you are calling the CULA routines by this line: "cula info: issuing to GPU"
- john
- Administrator
- Posts: 587
- Joined: Thu Jul 23, 2009 2:31 pm
2 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest