PA 0

HELLO CUDACS 791v Fall 2001

Makefile

# a simple makefile for building the sample program.# I use multiple versions of gcc, but cuda only supports# gcc 4.4 or lower. The ccbin command tells nvcc to use# gcc 4.4 as its regular (non-gpu) compiler.## the uncommented line should do the trick for you.

all: hicuda

hicuda: hellocuda.cu add.cu# nvcc -ccbin=/home/richard/bin/ $^ -o $@

nvcc $^ -o $@

clean:rm -f *.orm -f *~

hellocuda.cu (1)

/* This program demonstrates the basics of working with cuda. We use the GPU to add two arrays. We also introduce cuda's approach to error handling and timing using cuda Events.

This is the main program. You should also look at the header add.h for the important declarations, and then look at add.cu to see how to define functions that execute on the GPU. */

#include <iostream>

#include "add.h"

int main() { // Arrays on the host (CPU) int a[N], b[N], c[N]; /* These will point to memory on the GPU - notice the correspondence between these pointers and the arrays declared above. */ int *dev_a, *dev_b, *dev_c;

hellocuda.cu (2)

/* These calls allocate memory on the GPU (also called the device). This is similar to C's malloc, except that instead of directly returning a pointer to the allocated memory, cudaMalloc returns the pointer through its first argument, which must be a void**. The second argument is the number of bytes we want to allocate.

NB: the return value of cudaMalloc (like most cuda functions) is an error code. Strictly speaking, we should check this value and perform error handling if anything went wrong. We do this for the first call to cudaMalloc so you can see what it looks like, but for all other function calls we just point out that you should do error checking.

Actually, a good idea would be to wrap this error checking in a function or macro, which is what the Cuda By Example book does. */ cudaError_t err = cudaMalloc( (void**) &dev_a, N * sizeof(int)); if (err != cudaSuccess) { std::cerr << "Error: " << cudaGetErrorString(err) << std::endl; exit(1); } cudaMalloc( (void**) &dev_b, N * sizeof(int)); cudaMalloc( (void**) &dev_c, N * sizeof(int));

hellocuda.cu (3)

// These lines just fill the host arrays with some data so we can do // something interesting. Well, so we can add two arrays. for (int i = 0; i < N; ++i) { a[i] = i; b[i] = i; }

/* The following code is responsible for handling timing for code that executes on the GPU. The cuda approach to this problem uses events. For timing purposes, an event is essentially a point in time. We create events for the beginning and end points of the process we want to time. When we want to start timing, we call cudaEventRecord.

In this case, we want to record the time it takes to transfer data to the GPU, perform some computations, and transfer data back. */ cudaEvent_t start, end; cudaEventCreate(&start); cudaEventCreate(&end);

cudaEventRecord( start, 0 );

hellocuda.cu (3)

/* Once we have host arrays containing data and we have allocated memory on the GPU, we have to transfer data from the host to the device. Again, notice the similarity to C's memcpy function.

The first argument is the destination of the copy - in this case a pointer to memory allocated on the device. The second argument is the source of the copy. The third argument is the number of bytes we want to copy. The last argument is a constant that tells cudaMemcpy the direction of the transfer. */ cudaMemcpy(dev_a, a, N * sizeof(int), cudaMemcpyHostToDevice); cudaMemcpy(dev_b, b, N * sizeof(int), cudaMemcpyHostToDevice); cudaMemcpy(dev_c, c, N * sizeof(int), cudaMemcpyHostToDevice);

hellocuda.cu (4)

/* FINALLY we get to run some code on the GPU. At this point, if you haven't looked at add.cu (in this folder), you should. The comments in that file explain what the add function does, so here let's focus on how add is being called. The first thing to notice is the <<<...>>>, which you should recognize as _not_ being standard C. This syntactic extension tells nvidia's cuda compiler how to parallelize the execution of the function. We'll get into details as the course progresses, but for we'll say that <<<N, 1>>> is creating N _blocks_ of 1 _thread_ each. Each of these threads is executing add with a different data element (details of the indexing are in add.cu).

In larger programs, you will typically have many more blocks, and each block will have many threads. Each thread will handle a different piece of data, and many threads can execute at the same time. This is how cuda can get such large speedups. */ add<<<N, 1>>>(dev_a, dev_b, dev_c);

hellocuda.cu (5)/*

Unfortunately, the GPU is to some extent a black box. In order to print the results of our call to add, we have to transfer the data back to the host. We do that with a call to cudaMemcpy, which is just like the cudaMemcpy calls above, except that the direction of the transfer (given by the last argument) is reversed. In a real program we would want to check the error code returned by this function. */ cudaMemcpy(c, dev_c, N * sizeof(int), cudaMemcpyDeviceToHost);

/* This is the other end of the timing process. We record an event, synchronize on it, and then figure out the difference in time between the start and the stop.

We have to call cudaEventSynchronize before we can safely _read_ the value of the stop event. This is because the GPU may not have actually written to the event until all other work has finished. */ cudaEventRecord( end, 0 ); cudaEventSynchronize( end );

float elapsedTime; cudaEventElapsedTime( &elapsedTime, start, end );

hellocuda.cu (6)

/* Let's check that the results are what we expect. */ for (int i = 0; i < N; ++i) { if (c[i] != a[i] + b[i]) { std::cerr << "Oh no! Something went wrong. You should check your cuda install and your GPU. :(" << std::endl;

// clean up events - we should check for error codes here. cudaEventDestroy( start ); cudaEventDestroy( end );

// clean up device pointers - just like free in C. We don't have // to check error codes for this one. cudaFree(dev_a); cudaFree(dev_b); cudaFree(dev_c); exit(1); } }

hellocuda.cu (7)

/* Let's let the user know that everything is ok and then display some information about the times we recorded above. */ std::cout << "Yay! Your program's results are correct." << std::endl; std::cout << "Your program took: " << elapsedTime << " ms." << std::endl; // Cleanup in the event of success. cudaEventDestroy( start ); cudaEventDestroy( end );

cudaFree(dev_a); cudaFree(dev_b); cudaFree(dev_c);

} 

add.h

/* This header demonstrates how we build cuda programs spanning multiple files. */

#ifndef ADD_H_#define ADD_H_

// This is the number of elements we want to process.#define N 1024

// This is the declaration of the function that will execute on the GPU.__global__ void add(int*, int*, int*);

#endif // ADD_H_

add.cu (1)

#include "add.h"

/* This is the function that each thread will execute on the GPU. The fact that it executes on the device is indicated by the __global__ modifier in front of the return type of the function. After that, the signature of the function isn't special - in particular, the pointers we pass in should point to memory on the device, but this is not indicated by the function's signature. */__global__ void add(int *a, int *b, int *c) {

add.cu (2) /*

Each thread knows its identity in the system. This identity is made available in code via indices blockIdx and threadIdx. We write blockIdx.x because block indices are multidimensional. In this case, we have linear arrays of data, so we only need one dimension. If this doesn't make sense, don't worry - the important thing is that the first step in the function is converting the thread's indentity into an index into the data. */ int thread_id = blockIdx.x;

/* We make sure that the thread_id isn't too large, and then we assign c = a + b using the index we calculated above.

The big picture is that each thread is responsible for adding one element from a and one element from b. Each thread is able to run in parallel, so we get speedup. */ if (thread_id < N) { c[thread_id] = a[thread_id] + b[thread_id]; }}