CUDA and MPI

More documents

Recommendations

Info

CUDA 4.0 Enhancements
No-copy Pinning of System MemoryReduce system memory usage and CPU memcpy() overheadEasier to add CUDA acceleration to existing applicationsJust register malloc’d system memory for async operationsand then call cudaMemcpy() as usualBefore No-copy PinningExtra allocation and extra copy requiredAll CUDA-capable GPUs on Linux or WindowsRequires Linux kernel 2.6.15+ (RHEL 5)With No-copy PinningJust register and go!cudaMallocHost(b)memcpy(b, a)cudaHostRegister(a)cudaMemcpy() to GPU, launch kernels, cudaMemcpy() from GPUmemcpy(a, b)cudaFreeHost(b)malloc(a)cudaHostUnregister(a)
Page 1 and 2: CUDA and MPIDale SouthardSenior Sol
Page 3 and 4: What You’ve Learned So Far….Use
Page 5 and 6: Zero-Copy Memory before CUDA 4.0Sin
Page 7 and 8: The DMA/RDMA ProblemCUDA driver all
Page 9 and 10: What is GPUDirect?GPUDirect is an u
Page 11: 1GPUDirect v1CPUChipsetGPUInfiniBan
Page 15 and 16: Unified Virtual AddressingEasier to
Page 18 and 19: Multiple GPUs Before NVIDIA GPUDire
Page 20 and 21: GPUDirect v2.0: Peer-to-Peer Commun
Page 22 and 23: Topology and Locality
Page 24 and 25: And More TopologyMemoryMemoryMemory

CUDA and MPI

Create successful ePaper yourself

Delete template?

Save as template?