Accelerated Computing

Compiling MNIST on MacOSX [cudnn test]

2015-04-06T22:49:00.002-04:00

$ make

g++ -c -o mnistCUDNN.o mnistCUDNN.cpp -I. -I/usr/local/cuda/include -I/usr/local/cuda/cudnn  -I/opt/local/include -I/usr/local/cuda/samples/7_CUDALibraries/common/UtilNPP
gcc -o mnistCUDNN mnistCUDNN.o -L/usr/local/cuda/lib -L/usr/local/cuda/cudnn -L/opt/local/lib -lnppi -lnppc -lfreeimage -lcudart -lcublas -lcudnn -lm -lstdc++



$ ./mnistCUDNN 

Loading image data/one_28x28.pgm

Performing forward propagation ...

Resulting weights from Softmax:

4.05186e-07 0.999404 2.21383e-07 1.20837e-08 0.000587085 5.06682e-08 2.80583e-06 1.47965e-06 3.56051e-06 2.46337e-07 

Loading image data/three_28x28.pgm

Performing forward propagation ...

Resulting weights from Softmax:

4.67739e-05 5.83973e-07 1.76501e-06 0.75859 1.06138e-11 0.24133 2.62157e-10 1.11104e-05 3.39113e-07 1.88164e-05 

Loading image data/five_28x28.pgm

Performing forward propagation ...

Resulting weights from Softmax:

3.22452e-10 8.69774e-10 3.73033e-12 3.2219e-07 2.67785e-11 0.999992 4.58862e-06 5.08385e-10 9.35238e-07 1.87656e-06 




Result of classification: 1 3 5




Test passed!

Installing Caffe on Mac OSX 10.10

2015-04-06T22:24:00.000-04:00

Here are the instructions I followed for installing Caffe on Mac OSX 10.10

Clone the repository from here:

git clone https://github.com/BVLC/caffe
cp Makefile.config.example Makefile.config

Inside Makefile.config make the following changes:

PYTHON_LIB := $(ANACONDA_HOME)/lib
INCLUDE_DIRS := $(PYTHON_INCLUDE) /usr/local/include /opt/local/include /usr/local/cuda/cudnn
LIBRARY_DIRS := $(PYTHON_LIB) /usr/local/lib /usr/lib /opt/local/lib /usr/local/cuda/cudnn

Check the requirements.txt file:

Cython>=0.19.2
numpy>=1.7.1
scipy>=0.13.2
scikit-image>=0.9.3
matplotlib>=1.3.1
ipython>=1.1.0
h5py>=2.2.0
leveldb>=0.191
networkx>=1.8.1
nose>=1.3.0
pandas>=0.12.0
python-dateutil>=1.4,<2 protobuf="">=2.5.0
python-gflags>=2.0
pyyaml>=3.10
Pillow>=2.3.0

If you are using Anaconda:

$ for req in $(cat requirements.txt); do conda install $req; done

Compile and build:

$ make all
$ make py
$ make test
$ make runtest

$ export CAFFE_HOME=${HOME}/caffe

Latex help: where to save .cls and .bst files local on Mac

2013-08-15T13:51:00.002-04:00

Recently I was looking at options on where to save latex cls and bst files locally on my Mac and I came across this very good source from TeXStackEchange: How to have local package override default package

Most of the times I have the IEEEtran.bst files modified so that if I cite the same author twice, I would like to see the author's name again

% #0 turns off the "dashification" of repeated (i.e., identical to those
% of the previous entry) names. IEEE normally does this.
% #1 enables
FUNCTION {default.is.dash.repeated.names} { #0 }

and sometimes if an article has more than 6 authors, I want that reference shortened to et. al.

% The maximum number of names that can be present beyond which an "et al."
% usage is forced. Be sure that num.names.shown.with.forced.et.al (below)
% is not greater than this value!
% Note: There are many instances of references in IEEE journals which have
% a very large number of authors as well as instances in which "et al." is
% used profusely.

FUNCTION {default.max.num.names.before.forced.et.al} { #3 }

So as per the instructions, I created this structure:

1. For .cls files:

/Users/'username'/Library/texmf/tex/latex/

2. For .bst files:

/Users/'username'/Library/texmf/bibtex/bst/

Happy Latexing !

ERSA presentation comparing DSPs vs FPGAs vs GPUs

2011-07-31T15:42:00.001-04:00

I recently presented my work at the 2011 International Conference on
Engineering of Reconfigurable Systems and Algorithms (ERSA 2011) conference, held at Las Vegas, NV.

The three keynotes were:
1. How Engineering Mathematics can Improve Software by Prof. David Lorge Parnas
2. The Nature of Cyber Security by Prof. Eugene H. Spafford
3. Changing Lives around the World: the Power of Technology by Dr. Sandeep Chatterjee

All the keynotes were impressive and very diverse, started with applying engineering mathematics to a process; cyber security as a science and method; and finally mobile computing applications in developing countries. Though there are no slides to link for Dr. Chatterjee's talk, his talk had example scenarios where mobile computing was used for banking, construction, etc.

The ERSA sessions started with a bang and the tutorial session on evolvable computing by Prof. Jim Torresen was very interesting. The Evolvable And Bio-Inspired Hardware session by Dr. Eric Stahlberg was interesting where the convergence was on what biological process can inspire computing in general.

Finally, here's a link to my presentation on "Accelerating Real-time processing of the ATST Adaptive Optics System using Coarse-grained Parallel Hardware Architectures". My talk was on Wednesday July 20,2011 at the Gold Room.

I also chaired Session 13-PDPTA: Systems Software + OS + Programming Models + Architecture Issues +
Fault-Tolerant Systems & Tools on Thursday July 21, 2011 from 08:00am - 12:20pm (LOCATION: Ballroom 4) as part of the 2011 International Conference on Parallel and Distributed Processing Techniques and Applications (PDPTA'11).

Next year's ERSA is expected to be bigger and better and promises to have a developers meet/session. Eagerly looking forward to next year's conference.

Some great reference books for CUDA and OpenCL

2011-04-25T10:13:00.002-04:00

This is a list of some good reference books for CUDA and OpenCL:

1. CUDA by Example: An Introduction to General-Purpose GPU Programming Jason Sanders & Edward Kandrot For Kindle: CUDA by Example: An Introduction to General-Purpose GPU Programming

2. Programming Massively Parallel Processors: A Hands-on Approach (Applications of GPU Computing Series) David B. Kirk & Wen-mei W. Hwu For Kindle: Programming Massively Parallel Processors: A Hands-on Approach (Applications of GPU Computing Series)

3. CUDA Application Design and Development [Paperback] Rob Farber (Dr Dobbs series author) Excellent book with some good examples and overview into the CUDA+OpenGL interface.

4. Heterogeneous Computing with OpenCL Benedict Gaster, Lee Howes, David R. Kaeli, Perhaad Mistry, Dana Schaa

Installing pyCUDA-0.94.2 on CentOS 5.5

2010-12-22T19:22:00.002-05:00

Installing pyCUDA-0.94.2 can be quite a hassle on CentOS 5.5 Linus OS. As per couple of my posts to the pyCUDA list, I did use the correct parameters while configuring pyCUDA. However CentOS 5.5 ships with gcc-4.1.2 and that gives an error while installing pyCUDA. So I have posted my steps on how I installed pyCUDA-0.94.2 on CentOS 5.5:

Step 1: Change your default gcc to gcc-4.4 and g++ to g++-4.4. I used yum to install them.

$ cd /usr/bin
$ sudo rm /usr/bin/gcc
$ sudo ln -s /usr/bin/gcc44 /usr/bin/gcc
$ sudo rm /usr/bin/g++
$ sudo ln -s /usr/bin/g++44 /usr/bin/g++

Check your installation:


$ gcc -v
Using built-in specs.
Target: x86_64-redhat-linux6E
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,fortran --disable-libgcj --with-mpfr=/builddir/build/BUILD/gcc-4.4.0-20090514/obj-x86_64-redhat-linux6E/mpfr-install/ --with-ppl=/builddir/build/BUILD/gcc-4.4.0-20090514/obj-x86_64-redhat-linux6E/ppl-install --with-cloog=/builddir/build/BUILD/gcc-4.4.0-20090514/obj-x86_64-redhat-linux6E/cloog-install --with-tune=generic --with-arch_32=i586 --build=x86_64-redhat-linux6E
Thread model: posix
gcc version 4.4.0 20090514 (Red Hat 4.4.0-6) (GCC)


$ g++ -v
Using built-in specs.
Target: x86_64-redhat-linux6E
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,fortran --disable-libgcj --with-mpfr=/builddir/build/BUILD/gcc-4.4.0-20090514/obj-x86_64-redhat-linux6E/mpfr-install/ --with-ppl=/builddir/build/BUILD/gcc-4.4.0-20090514/obj-x86_64-redhat-linux6E/ppl-install --with-cloog=/builddir/build/BUILD/gcc-4.4.0-20090514/obj-x86_64-redhat-linux6E/cloog-install --with-tune=generic --with-arch_32=i586 --build=x86_64-redhat-linux6E
Thread model: posix
gcc version 4.4.0 20090514 (Red Hat 4.4.0-6) (GCC)

Step 2:  Unzip pycuda-0.94.2 to your directory and install numpy, pytest and pytools

$ tar xzf pycuda-0.94.2.tar.gz
$ sudo easy_install numpy
install_dir /usr/local/lib/python2.6/site-packages/
Searching for numpy
Best match: numpy 1.5.1
Processing numpy-1.5.1-py2.6-linux-x86_64.egg
numpy 1.5.1 is already the active version in easy-install.pth
Installing f2py script to /usr/local/bin

Using /usr/local/lib/python2.6/site-packages/numpy-1.5.1-py2.6-linux-x86_64.egg
Processing dependencies for numpy
Finished processing dependencies for numpy

$ sudo easy_install pytest
install_dir /usr/local/lib/python2.6/site-packages/
Searching for pytest
Reading http://pypi.python.org/simple/pytest/
Reading http://pytest.org
Best match: pytest 2.0.0
Downloading http://pypi.python.org/packages/source/p/pytest/pytest-2.0.0.zip#md5=f07c521dfd5a540f3dfea1846e58dab7
Processing pytest-2.0.0.zip
Running pytest-2.0.0/setup.py -q bdist_egg --dist-dir /tmp/easy_install-5pyoXO/pytest-2.0.0/egg-dist-tmp-ssbYCg
Adding pytest 2.0.0 to easy-install.pth file
Installing py.test script to /usr/local/bin
Installing py.test-2.6 script to /usr/local/bin

Installed /usr/local/lib/python2.6/site-packages/pytest-2.0.0-py2.6.egg
Processing dependencies for pytest
Finished processing dependencies for pytest


$ sudo easy_install pytools
install_dir /usr/local/lib/python2.6/site-packages/
Searching for pytools
Best match: pytools 11
Processing pytools-11-py2.6.egg
pytools 11 is already the active version in easy-install.pth
Installing runalyzer-gather script to /usr/local/bin
Installing runalyzer script to /usr/local/bin
Installing logtool script to /usr/local/bin

Using /usr/local/lib/python2.6/site-packages/pytools-11-py2.6.egg
Processing dependencies for pytools
Finished processing dependencies for pytools

Step 3: Configure siteconf.py

$ python configure.py --cuda-root=/usr/local/cuda --cudadrv-lib-dir=/usr/lib64/nvidia --boost-inc-dir=/usr/include --boost-lib-dir=/usr/local/lib CXXFLAGS=-DBOOST_PYTHON_NO_PY_SIGNATURES

Step 4: Install

$ sudo make install

Step 5: Test your installation

$ python test/test_driver.py 
=============================================================== test session starts ===============================================================
platform linux2 -- Python 2.6.6 -- pytest-2.0.0
collected 18 items 

test/test_driver.py ..................

============================================================ 18 passed in 4.58 seconds ========================================

If you see the message above, pyCuda should be working now. Enjoy :)

FYI: For installing pyCuda on Ubuntu 10.10, refer to http://wiki.tiker.net/PyCuda/Installation/Linux/Ubuntu

Installing Tesla C2050 and C1060 on Centos

2010-10-07T17:44:00.018-04:00

I have been waiting to get a NVIDIA Fermi GPU to prototype my algorithms, but I was waiting to get an optimized implementation on the Tesla C1060 and then scale up to the Fermi. I got a C2050 and set about installing it on my machine. (note: my host machine is a Lian-Li PC with an integrated NVIDIA nForce 980a/780a (8 cores).

Installing the C2050 was easy, it has 2 power connections (6-pin and 8-pin). In most of the cases, connecting the 8-pin connector is more than enough.

After installing the C2050, I had to boot the machine and change the BIOS setting to disable display from external GPUs. The C2050 has a display out and I don't intend to use it now.

My deviceQuery output:

[vivekv@atstgpu release]$ more deviceQuery.txt
./deviceQuery Starting...
 CUDA Device Query (Runtime API) version (CUDART static linking)
There are 3 devices supporting CUDA
Device 0: "Tesla C2050"
  CUDA Driver Version:                           3.10
  CUDA Runtime Version:                          3.10
  CUDA Capability Major revision number:         2
  CUDA Capability Minor revision number:         0
  Total amount of global memory:                 3220897792 bytes
  Number of multiprocessors:                     14
  Number of cores:                               448
  Total amount of constant memory:               65536 bytes
  Total amount of shared memory per block:       49152 bytes
  Total number of registers available per block: 32768
  Warp size:                                     32
  Maximum number of threads per block:           1024
  Maximum sizes of each dimension of a block:    1024 x 1024 x 64
  Maximum sizes of each dimension of a grid:     65535 x 65535 x 1
  Maximum memory pitch:                          2147483647 bytes
  Texture alignment:                             512 bytes
  Clock rate:                                    1.15 GHz
  Concurrent copy and execution:                 Yes
  Run time limit on kernels:                     No
  Integrated:                                    No
  Support host page-locked memory mapping:       Yes
  Compute mode:                                  Default (multiple host threads can use this device simultaneously)
  Concurrent kernel execution:                   Yes
  Device has ECC support enabled:                No
Device 1: "Tesla C1060"
  CUDA Driver Version:                           3.10
  CUDA Runtime Version:                          3.10
  CUDA Capability Major revision number:         1
  CUDA Capability Minor revision number:         3
  Total amount of global memory:                 4294770688 bytes
  Number of multiprocessors:                     30
  Number of cores:                               240
  Total amount of constant memory:               65536 bytes
  Total amount of shared memory per block:       16384 bytes
  Total number of registers available per block: 16384
  Warp size:                                     32
  Maximum number of threads per block:           512
  Maximum sizes of each dimension of a block:    512 x 512 x 64
  Maximum sizes of each dimension of a grid:     65535 x 65535 x 1
  Maximum memory pitch:                          2147483647 bytes
  Texture alignment:                             256 bytes
  Clock rate:                                    1.30 GHz
  Concurrent copy and execution:                 Yes
  Run time limit on kernels:                     No
  Integrated:                                    No
  Support host page-locked memory mapping:       Yes
  Compute mode:                                  Default (multiple host threads can use this device simultaneously)
  Concurrent kernel execution:                   No
  Device has ECC support enabled:                No
Device 2: "nForce 980a/780a SLI"
  CUDA Driver Version:                           3.10
  CUDA Runtime Version:                          3.10
  CUDA Capability Major revision number:         1
  CUDA Capability Minor revision number:         1
  Total amount of global memory:                 131399680 bytes
  Number of multiprocessors:                     1
  Number of cores:                               8
  Total amount of constant memory:               65536 bytes
  Total amount of shared memory per block:       16384 bytes
  Total number of registers available per block: 8192
  Warp size:                                     32
  Maximum number of threads per block:           512
  Maximum sizes of each dimension of a block:    512 x 512 x 64
  Maximum sizes of each dimension of a grid:     65535 x 65535 x 1
  Maximum memory pitch:                          2147483647 bytes
  Texture alignment:                             256 bytes
  Clock rate:                                    1.20 GHz
  Concurrent copy and execution:                 No
  Run time limit on kernels:                     Yes
  Integrated:                                    Yes
  Support host page-locked memory mapping:       Yes
  Compute mode:                                  Default (multiple host threads can use this device simultaneously)
  Concurrent kernel execution:                   No
  Device has ECC support enabled:                No
deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 3.10, CUDA Runtime Version = 3.10, NumDevs = 3, Device = Tesla C2050, Device = Tesla 
C1060

PASSED
Press <Enter> to Quit...
-----------------------------------------------------------

I hope to post the performance comparison of my kernels using the Tesla C2050 sometime soon.

CUDA and Computational Finance

2009-10-24T09:51:00.003-04:00

Saw this on my Google Reader list and wanted to share it with everyone. This URL contains some videos/presentations on using CUDA for Computational Finance. (thanks to Argyn)

Lots more CUDA tutorials coming at SC09 !!!

Installing Boost C++ libraries

2009-10-20T17:10:00.025-04:00

I know that installing Boost C++ libraries has nothing to do with GPGPU and multi-cores. Nevertheless, I have posted my procedure for installing Boost C++ libraries on a Mac.

I use Macports on my Mac and I find that it is the easiest way to install any open-source software on Mac OSX.

1. Search for boost packages

bash-3.2$ sudo port search boost

boost @1.40.0 (devel)

Collection of portable C++ source libraries

boost-build @2.0-m12 (devel)

Build system for large project software construction

boost-gil-numeric @1.0 (devel)

An algorithm extension to boost-gil.

boost-jam @3.1.17 (devel)

Boost.Jam (BJam) is a build tool based on FTJam

py26-pyplusplus @1.0.0 (python, devel)

Py++ is an framework for creating a code generator for Boost.Python library and ctypes package

Found 5 ports.

2. Install

bash-3.2$ sudo port install boost-jam

---> Fetching boost-jam

---> Verifying checksum for boost-jam

---> Extracting boost-jam

---> Configuring boost-jam

---> Building boost-jam with target all

---> Staging boost-jam into destroot

---> Installing boost-jam

bash-3.2$ sudo port install boost

---> Fetching boost

---> Verifying checksum for boost

---> Extracting boost

---> Configuring boost

---> Building boost with target all

---> Staging boost into destroot

---> Installing boost

bash-3.2$ sudo port install boost-build

---> Fetching boost-build

---> Verifying checksum for boost-build

---> Extracting boost-build

---> Configuring boost-build

---> Building boost-build with target all

---> Staging boost-build into destroot

---> Installing boost-build

3. Here's my example program:

#include <iostream>

#include <boost/any.hpp>

using namespace std;

int main()

{

boost::any

a(5);

a = 7.67;

std:cout<<boost::any_cast<double>(a)<<std::endl;

}

Now when I tried compiling my example program, I got a lot of errors such as:

example3.cpp:11:25: error: boost/any.hpp: No such file or directory

example3.cpp: In function ‘int main()’:

example3.cpp:18: error: ‘boost’ has not been declared

example3.cpp:18: error: ‘any’ was not declared in this scope

example3.cpp:18: error: expected `;' before ‘a’

example3.cpp:19: error: ‘a’ was not declared in this scope

example3.cpp:20: error: ‘boost’ has not been declared

example3.cpp:20: error: ‘any_cast’ was not declared in this scope

example3.cpp:20: error: expected primary-expression before ‘double’

example3.cpp:20: error: expected `;' before ‘double’

So I googled around and came to this link and tried compiling using the full path:

$ g++ -I /opt/local/var/macports/software/boost/1.40.0_1/opt/local/include/ example3.cpp -o example3_new

and that worked...!!!!

I also did this as a shortcut for compiling my programs that need the Boost libraries:

$ export BOOST=/opt/local/var/macports/software/boost/1.40.0_1/opt/local/include/

$ echo $BOOST

/opt/local/var/macports/software/boost/1.40.0_1/opt/local/include/

$ g++ -I $BOOST example3.cpp -o example3_new

$./example3_new

7.67

Hope this helps :)

OpenCL drivers available from Nvidia

2009-09-28T19:54:00.003-04:00

OpenCL drivers are available for download from Nvidia.

You can download the SDK, Best Practices guide from here: Nvidia OpenCL download

Waiting to try some sample code examples using OpenCL and evaluate how it differs from CUDA :)

SAAHPC presentation

2009-08-19T10:26:00.002-04:00

I recently presented my work at the SAAHPC conference, held at NCSA Urbana, IL. The Keynote talk was by Pradeep Dubey on Massive Data Computing using Intel Larrabee. Excellent overview on why data transfer and management is the challenge in today's computing. I liked the Connected Computing factor - Content, Connect and Compute. I have found out from real-time problems that having the fastest computation platform is not enough, it's even more important to sustain the streaming bandwidth of the data into the platform. Obviously, once the data is inside the memory, computation is fast. But the real bottleneck is in importing and offloading the data and trying to streamline and synchronize the data (some of my PhD dissertation grumble).

I liked the talk by Michael Garland on GPU Computing using CUDA. This was informative in terms of his insight on the Thrust template. Thrust is open source and is hosted on Google Code. I have to start using this for my next CUDA project.

Finally, here's a link to my presentation on "Accelerating Particle Image Velocimetry using Hybrid Architectures".

Installing CUDA 2.3

2009-07-31T10:13:00.000-04:00

Installing CUDA 2.3 is pretty easy and straightforward. However, on my Mac, the CUDA SDK examples are now in

/Developer/GPU Computing

In addition to the drivers for Leopard, there's a separate version for Snow Leopard :) New documentation includes the CUDA Best Practices Guide. This is the correct link, thanks to the NVIDIA forums post. The CUDA Resource page does not point you to the correct link.

Have a good time accelerating your apps using CUDA :)

cuda-gdb error on CentOS

2009-06-29T10:21:00.007-04:00

CUDA 2.2 comes with its native debugger support through cuda-gdb. However, I had some problems configuring cuda-gdb on my Linux distro (CentOS).

When I execute cuda-gdb fresh after my installation, here's what I see:

$ cuda-gdb

cuda-gdb: error while loading shared libraries: libtermcap.so.2: cannot open shared object file: No such file or directory

I tried searching for the missing library libtermcap.so.2 using

locate libtermcap

A google search led me to http://forums.nvidia.com/index.php?showtopic=96987

and I installed libncurses and linked it correctly.

sudo yum install ncurses.x86_64

sudo ln -s /usr/lib64/libncurses.so /usr/local/cuda/lib/libtermcap.so.2

That seemed to do the trick !!!

$ cuda-gdb

NVIDIA (R) CUDA Debugger

BETA release

GNU gdb 6.6

GDB is free software, covered by the GNU General Public License, and you are

welcome to change it and/or distribute copies of it under certain conditions.

Type "show copying" to see the conditions.

There is absolutely no warranty for GDB. Type "show warranty" for details.

This GDB was configured as "x86_64-unknown-linux-gnu".

(cuda-gdb)

For more info on cuda-gdb refer to: http://developer.download.nvidia.com/compute/cuda/2_2/toolkit/docs/CUDA_GDB_User_Manual_2.2beta.pdf

Installing CUDA 2.2 on MacPro running CentOS 64-bit

2009-05-12T22:34:00.010-04:00

My test machine is an early 200 Mac Pro with a NVIDIA Tesla C1060. Upgrading to CUDA 2.2 on this Mac was relatively easy. Please read my previous post for installing CUDA 2.1 before attempting to install CUDA 2.2 on a CentOS 64-bit distro.

Step 1: Download packages:

wget http://developer.download.nvidia.com/compute/cuda/2_2/drivers/cudadriver_2.2_linux_64_185.18.08-beta.run
wget http://developer.download.nvidia.com/compute/cuda/2_2/toolkit/cudatoolkit_2.2_linux_64_rhel5.3.run
wget http://developer.download.nvidia.com/compute/cuda/2_2/sdk/cudasdk_2.2_linux.run
wget http://developer.download.nvidia.com/compute/cuda/2_2/toolkit/cudagdb_2.2_linux_64_rhel5.3.run

Change permissions

chmod +x cudadriver_2.2_linux_64_185.18.08-beta.run
chmod +x cudatoolkit_2.2_linux_64_rhel5.3.run
chmod +x cudagdb_2.2_linux_64_rhel5.3.run
chmod +x cudasdk_2.2_linux.run

Step 2: Find your kernel source and install the corresponding kernel-devel and kernel-headers:

uname -r
2.6.27.21-170.2.56.fc10.x86_64

sudo yum install kernel-devel
sudo yum install kernel-headers

Step 3: Install the CUDA driver first, followed by the toolkit, gdb and finally the SDK.

sudo ./cudadriver_2.2_linux_64_185.18.08-beta.run --kernel-source-path /usr/src/kernels/2.6.27.21-170.2.56.fc10.x86_64
sudo ./cudatoolkit_2.2_linux_64_rhel5.3.run
sudo ./cudagdb_2.2_linux_64_rhel5.3.run
./cudasdk_2.2_linux.run

Make sure that your path is configured correctly. (Refer to previous post)

Step 4: Enable the cuda script mentioned in the previous post.

sudo service cuda start

check the nvidia driver status and you should see this:

ls /dev/nv*
/dev/nvidia0  /dev/nvidiactl  /dev/nvram

Step 5: Make sure you do a fresh install of the SDK if you are upgrading.

cd NVIDIA_CUDA_SDK/
make

This should make all your projects in the following directory:

$HOME/NVIDIA_CUDA_SDK/bin/linux/release

Executing the deviceQuery executable shows me this:

./deviceQuery
CUDA Device Query (Runtime API) version (CUDART static linking)
There is 1 device supporting CUDA

Device 0: "Tesla C1060"
CUDA Capability Major revision number:         1
CUDA Capability Minor revision number:         3
Total amount of global memory:                 4294705152 bytes
Number of multiprocessors:                     30
Number of cores:                               240
Total amount of constant memory:               65536 bytes
Total amount of shared memory per block:       16384 bytes
Total number of registers available per block: 16384
Warp size:                                     32
Maximum number of threads per block:           512
Maximum sizes of each dimension of a block:    512 x 512 x 64
Maximum sizes of each dimension of a grid:     65535 x 65535 x 1
Maximum memory pitch:                          262144 bytes
Texture alignment:                             256 bytes
Clock rate:                                    1.30 GHz
Concurrent copy and execution:                 Yes
Run time limit on kernels:                     No
Integrated:                                    No
Support host page-locked memory mapping:       Yes
Compute mode:                                  Default (multiple host threads can use this device simultaneously)

Test PASSED

Press ENTER to exit...

Congrats !!! CUDA 2.2 is configured on your 64-bit CentOS Mac Pro and also recognizes the NVIDIA Tesla C1060. Looking forward to post some examples with the zero copy feature :)

Installing CUDA 2.2 on Mac OSX

2009-05-08T15:15:00.003-04:00

Installing CUDA 2.2 on Mac OSX is pretty trivial. Only warning/suggestion: manually remove the CUDA 2.1 SDK directory from /Developer/CUDA
Do a fresh install (always recommended).

I tried upgrading without removing CUDA 2.1 SDK and saw my image denoising project failing to compile. This was the error I saw: "ld: duplicate symbol _cutFree in ../../lib/libcutil.a(cutil.cpp.o)"

My deviceQuery output:

hogwarts:emurelease vivekv$ ./deviceQuery
CUDA Device Query (Runtime API) version (CUDART static linking)
There is no device supporting CUDA.

Device 0: "Device Emulation (CPU)"
  CUDA Capability Major revision number:         9999
  CUDA Capability Minor revision number:         9999
  Total amount of global memory:                 4294967295 bytes
  Number of multiprocessors:                     16
  Number of cores:                               128
  Total amount of constant memory:               65536 bytes
  Total amount of shared memory per block:       16384 bytes
  Total number of registers available per block: 8192
  Warp size:                                     1
  Maximum number of threads per block:           512
  Maximum sizes of each dimension of a block:    512 x 512 x 64
  Maximum sizes of each dimension of a grid:     65535 x 65535 x 1
  Maximum memory pitch:                          262144 bytes
  Texture alignment:                             256 bytes
  Clock rate:                                    1.35 GHz
  Concurrent copy and execution:                 No
  Run time limit on kernels:                     No
  Integrated:                                    Yes
  Support host page-locked memory mapping:       Yes
  Compute mode:                                  Default (multiple host threads can use this device simultaneously)

Test PASSED

Press ENTER to exit...

I shall also post my experience installing CUDA 2.2 on a MacPro running CentOS 64-bit.

Learning CUDA

2009-03-09T08:59:00.003-04:00

I was planning to share some of my programming exercises here, but then I thought of sharing some of the CUDA resources I have collected in the past two months. This may not be an exhaustive list of all available resources, but they have benefited me immensely.
1. CUDA Programming Guide
2. CUDA Reference Manual
3. cuFFT Library Guide
For the above documents and more, you can always visit the CUDAZone and download the documents for your OS and release version.
4. Learning CUDA from NVIDIA: This page has some podcasts, slides from conferences and a link to Dr. Dobb's article series on CUDA. Another excellent link is the ECE498AL class taught at UIUC. I also liked the SC08 CUDA tutorial/Workshop, which I attended.
5. NVIDIA forums: When in doubt, post your query on the NVIDIA forums. Someone may have seen the same problem and is likely to post a answer.

Send me an email for the SC08 slides if you haven't found them on the Internet already.

Installing Nvidia Tesla C1060 on a Mac Pro with CentOS

2009-02-21T08:45:00.007-05:00

After my last post on getting CUDA 2.0 to run on my Mac, I will go through the steps for installing a Nvidia Tesla C1060 on a early 2008 Mac Pro with CentOS or equivalent RHEL 5.xx Linux distro. The Tesla C1060 has 240 streaming processor cores (1.3 GHz), 4GB onboard memory, requires PCIe x16, occupies two slots and has a 6-pin and 8-pin connector.

Instructions:

1. Physical install: Please download the C1060 User Manual and go through it before installing the C1060 physically. The C1060 has two connectors 6-pin and 8-pin, for a Mac Pro please please order the Booster cable (that's the correct Apple jargon). The booster cable is mentioned in the Mac Pro documentation to connect the Nvidia Quadro FX 5600. After inserting the C1060, refer to page 16 of the manual to see the LED status. Red indicates something wrong in connecting the booster cables. (As an afterthought, if you have a PC, you can buy the standard 6-pin/8-pin connector from Newegg for about $6.99)

2. Software install: Step 1: Get the latest CUDA drivers, toolkit and SDK from here. I selected the CUDA 2.1 drivers for Linux 64-bit for RHEL 5.xx. (You can paste the code directly to your terminal)

wget http://developer.download.nvidia.com/compute/cuda/2_1/drivers/NVIDIA-Linux-x86_64-180.22-pkg2.run
wget http://developer.download.nvidia.com/compute/cuda/2_1/toolkit/cudatoolkit_2.1_linux64_rhel5.2.run
wget http://developer.download.nvidia.com/compute/cuda/2_1/SDK/cuda-sdk-linux-2.10.1215.2015-3233425.run

Change permissions on the downloaded files

chmod +x NVIDIA-Linux-x86_64-180.22-pkg2.run
chmod +x cuda-sdk-linux-2.10.1215.2015-3233425.run
chmod +x cudatoolkit_2.1_linux64_rhel5.2.run

Step 2: Install the following packages or see if you have them installed on your system already.

sudo yum install freeglut-devel
sudo yum install libXi-devel

Step 3: Install the CUDA driver first, the toolkit and the SDK finally.

sudo ./NVIDIA-Linux-x86_64-180.22-pkg2.run
sudo ./cudatoolkit_2.1_linux64_rhel5.2.run
./cuda-sdk-linux-2.10.1215.2015-3233425.run

The Nvidia driver build the kernel for the Linux distro, if it cannot find the precompiled kernel. Click yes and go on. The toolkit installs cuda to /usr/local/cuda by default. The SDK installs into the NVIDIA_CUDA_SDK directory in your home folder by default.

Paste the following in your terminal (thanks to the Ubuntu instructions here)

echo "# CUDA stuff
PATH=\$PATH:/usr/local/cuda/bin
LD_LIBRARY_PATH=\$LD_LIBRARY_PATH:/usr/local/cuda/lib
export PATH
export LD_LIBRARY_PATH" >> ~/.bashrc

Step 4: On a RHEL Linux distro, a startup script is required to turn on and off the Nvidia device. This startup script is posted on the Nvidia forums.

#!/bin/bash
#
# Startup/shutdown script for nVidia CUDA
#
# chkconfig: 345 80 20
# description: Startup/shutdown script for nVidia CUDA

# Source function library.
. /etc/init.d/functions

DRIVER=nvidia
RETVAL=0

# Create /dev nodes for nvidia devices
function createnodes() {
   # Count the number of NVIDIA controllers found.
  N3D=`/sbin/lspci | grep -i NVIDIA | grep "3D controller" | wc -l`
  NVGA=`/sbin/lspci | grep -i NVIDIA | grep "VGA compatible controller" | wc -l`

  N=`expr $N3D + $NVGA - 1`
  for i in `seq 0 $N`; do
       mknod -m 666 /dev/nvidia$i c 195 $i
      RETVAL=$?
      [ "$RETVAL" = 0 ] || exit $RETVAL
   done

  mknod -m 666 /dev/nvidiactl c 195 255
  RETVAL=$?
  [ "$RETVAL" = 0 ] || exit $RETVAL
}

# Remove /dev nodes for nvidia devices
function removenodes() {
   rm -f /dev/nvidia*
}

# Start daemon
function start() {
   echo -n $"Loading $DRIVER kernel module: "
  modprobe $DRIVER && success || failure
  RETVAL=$?
  echo
  [ "$RETVAL" = 0 ] || exit $RETVAL

  echo -n $"Initializing CUDA /dev entries: "
  createnodes && success || failure
  RETVAL=$?
  echo
  [ "$RETVAL" = 0 ] || exit $RETVAL
}

# Stop daemon
function stop() {
   echo -n $"Unloading $DRIVER kernel module: "
  rmmod -f $DRIVER && success || failure
  RETVAL=$?
  echo
  [ "$RETVAL" = 0 ] || exit $RETVAL

  echo -n $"Removing CUDA /dev entries: "
  removenodes && success || failure
  RETVAL=$?
  echo
  [ "$RETVAL" = 0 ] || exit $RETVAL
}

# See how we were called
case "$1" in
   start)
       start
      ;;
   stop)
       stop
      ;;
   restart)
       stop
      start
      ;;
   *)
       echo $"Usage: $0 {start|stop|restart}"
      RETVAL=1
esac
exit $RETVAL

Copy this startup script into a file, "cuda_startup_script".

cp $HOME/cuda_drivers_2.1/cuda_startup_script cuda
cp cuda /etc/init.d/cuda
chmod 755 /etc/init.d/cuda
chkconfig --add cuda
chkconfig cuda on
service cuda start

After this, check if the device is recognized by executing

ls /dev/nv*

You should see the following in your terminal

/dev/nvidia0  /dev/nvidiactl  /dev/nvram

The "/dev/nvidiactl" indicates that the Nvidia card is recognized on your system. This is necessary when you need to compile your projects in the SDK/projects folder.

Also, on executing a lspci, you should see the following:

sudo /sbin/lspci -d "10de:*" -v -xxx
02:00.0 3D controller: nVidia Corporation Unknown device 05e7 (rev a1)
 Subsystem: nVidia Corporation Unknown device 066a
 Flags: bus master, fast devsel, latency 0, IRQ 193
 Memory at 96000000 (32-bit, non-prefetchable) [size=16M]
 Memory at 90000000 (64-bit, prefetchable) [size=64M]
 Memory at 94000000 (64-bit, non-prefetchable) [size=32M]
 I/O ports at 3000 [size=128]
 [virtual] Expansion ROM at 97000000 [disabled] [size=512K]
 Capabilities: [60] Power Management version 3
 Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
 Capabilities: [78] Express Endpoint IRQ 0
00: de 10 e7 05 07 00 10 00 a1 00 02 03 00 00 00 00
10: 00 00 00 96 0c 00 00 90 00 00 00 00 04 00 00 94
20: 00 00 00 00 01 30 00 00 00 00 00 00 de 10 6a 06
30: 00 00 00 00 60 00 00 00 00 00 00 00 0b 01 00 00
40: de 10 6a 06 00 00 00 00 00 00 00 00 00 00 00 00
50: 01 00 00 00 01 00 00 00 ce d6 23 00 00 00 00 00
60: 01 68 03 00 08 00 00 00 05 78 80 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 10 00 01 00 e0 84 00 00
80: 10 29 00 00 01 3d 00 08 08 00 01 01 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Step 5:

cd NVIDIA_CUDA_SDK/
make

This should make all your projects in the following directory

$HOME/NVIDIA_CUDA_SDK/bin/linux/release

Execute the deviceQuery executable should show this:

./deviceQuery
There is 1 device supporting CUDA

Device 0: "Tesla C1060"
 Major revision number:                         1
 Minor revision number:                         3
 Total amount of global memory:                 4294705152 bytes
 Number of multiprocessors:                     30
 Number of cores:                               240
 Total amount of constant memory:               65536 bytes
 Total amount of shared memory per block:       16384 bytes
 Total number of registers available per block: 16384
 Warp size:                                     32
 Maximum number of threads per block:           512
 Maximum sizes of each dimension of a block:    512 x 512 x 64
 Maximum sizes of each dimension of a grid:     65535 x 65535 x 1
 Maximum memory pitch:                          262144 bytes
 Texture alignment:                             256 bytes
 Clock rate:                                    1.30 GHz
 Concurrent copy and execution:                 Yes

Test PASSED

Press ENTER to exit...

Congratulations !!! Your Nvidia Tesla C1060 is configured on your system running CentOS or a similar RHEL distro. I shall post some exercises soon. For further questions, refer to the Nvidia forums.

Installing CUDA 2.0 on Mac OS

2009-02-13T20:04:00.011-05:00

I have setup CUDA 2.0 on my MacBook and these are the steps I followed:
1. Download the CUDA driver, toolkit and SDK samples from here: Get CUDA
2. Install the packages. The default location for the SDK is

/Developer/CUDA

3. Update your .profile or .bash_profile with the following lines:

export PATH=/usr/local/cuda/bin:$PATH
export DYLD_LIBRARY_PATH=/usr/local/cuda/lib:$DYLD_LIBRARY_PATH

4. Now the SDK comes with sample projects. If your Mac does not have a CUDA supported GPU, you can build the sample projects using the emulation mode.

cd /Developer/CUDA
make emu=1

All the binaries will be located in the folder

/Developer/CUDA/bin/darwin/emurelease

Have fun with the sample projects. I shall soon post my first CUDA program.