Cuda 2.2 Released.
NVIDIA CUDA
Linux Release Notes
Version 2.2
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
On some Linux releases, due to a GRUB bug in the handling of upper
memory and a default vmalloc too small on 32-bit systems, it may be
necessary to pass this information to the bootloader:
vmalloc=256MB, uppermem=524288
Example of grub conf:
title Red Hat Desktop (2.6.9-42.ELsmp)
root (hd0,0)
uppermem 524288
kernel /vmlinuz-2.6.9-42.ELsmp ro root=LABEL=/1 rhgb quiet vmalloc=256MB
pci=nommconf
initrd /initrd-2.6.9-42.ELsmp.img
--------------------------------------------------------------------------------
New Features
--------------------------------------------------------------------------------
Hardware Support
o See http://www.nvidia.com/object/cuda_learn_products.html
Platform Support
o Additional OS support
- Red Hat Enterprise Linux 5.3
- SUSE Linux 11.1
- Fedora 10
- Ubuntu 8.10
o Eliminated OS support
- SUSE Linux 10.3
- Fedora 8
- Ubuntu 7.10
API Features
o Pinned Memory Support
- These new memory management functions (cuMemHostAlloc() and
cudaHostAlloc()) enable pinned memory to be made "portable" (available
to all CUDA contexts), "mapped" (mapped into the CUDA address space),
and/or "write combined" (not cached and faster for the GPU to access).
- cuMemHostAlloc
- cuMemHostGetDevicePointer
- cudaHostAlloc
- cudaHostGetDevicePointer
o Function attribute query
- This function allows applications to query various function properties.
- cuFuncGetAttribute
o 2D Texture reads from pitch linear memory
- You can bind linear memory that you get from cuMemAlloc() or
cudaMalloc() directly to a 2D texture. In previous releases, you were
only able to bind cuArrayCreate() or cudaMallocArray() arrays to 2D
textures.
- cuTexRefSetAddress2D
- cudaBindTexture2D
o Flags for event creation
- Applications can now create events that use blocking synchronization.
- cudaEventCreateWithFlags
o New device management and context creation flags
- The function cudaSetDeviceFlags() allows the application to specify
attributes such as mapping host memory and support for blocking
synchronization.
- cudaSetDeviceFlags
o Improved runtime device management
- The runtime now defaults to attempting context creation on other
devices in the system before returning any failure messages. The new
call cudaSetValidDevices() allows the application to specify a list of
acceptable devices for use.
- cudaSetValidDevices
o Driver/runtime version query functions
- Applications can now directly query version information about the
underlying driver/runtime.
- cuDriverGetVersion
- cudaDriverGetVersion
- cudaRuntimeGetVersion
o New device attribute queries
- CU_DEVICE_ATTRIBUTE_INTEGRATED
- CU_DEVICE_ATTRIBUTE_CAN_MAP_HOST_MEMORY
- CU_DEVICE_ATTRIBUTE_COMPUTE_MODE
Documentation
o Doxygen-generated and cross-referenced html, pdf, and man pages.
- Runtime API
- Driver API
Linux Release Notes
Version 2.2
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
On some Linux releases, due to a GRUB bug in the handling of upper
memory and a default vmalloc too small on 32-bit systems, it may be
necessary to pass this information to the bootloader:
vmalloc=256MB, uppermem=524288
Example of grub conf:
title Red Hat Desktop (2.6.9-42.ELsmp)
root (hd0,0)
uppermem 524288
kernel /vmlinuz-2.6.9-42.ELsmp ro root=LABEL=/1 rhgb quiet vmalloc=256MB
pci=nommconf
initrd /initrd-2.6.9-42.ELsmp.img
--------------------------------------------------------------------------------
New Features
--------------------------------------------------------------------------------
Hardware Support
o See http://www.nvidia.com/object/cuda_learn_products.html
Platform Support
o Additional OS support
- Red Hat Enterprise Linux 5.3
- SUSE Linux 11.1
- Fedora 10
- Ubuntu 8.10
o Eliminated OS support
- SUSE Linux 10.3
- Fedora 8
- Ubuntu 7.10
API Features
o Pinned Memory Support
- These new memory management functions (cuMemHostAlloc() and
cudaHostAlloc()) enable pinned memory to be made "portable" (available
to all CUDA contexts), "mapped" (mapped into the CUDA address space),
and/or "write combined" (not cached and faster for the GPU to access).
- cuMemHostAlloc
- cuMemHostGetDevicePointer
- cudaHostAlloc
- cudaHostGetDevicePointer
o Function attribute query
- This function allows applications to query various function properties.
- cuFuncGetAttribute
o 2D Texture reads from pitch linear memory
- You can bind linear memory that you get from cuMemAlloc() or
cudaMalloc() directly to a 2D texture. In previous releases, you were
only able to bind cuArrayCreate() or cudaMallocArray() arrays to 2D
textures.
- cuTexRefSetAddress2D
- cudaBindTexture2D
o Flags for event creation
- Applications can now create events that use blocking synchronization.
- cudaEventCreateWithFlags
o New device management and context creation flags
- The function cudaSetDeviceFlags() allows the application to specify
attributes such as mapping host memory and support for blocking
synchronization.
- cudaSetDeviceFlags
o Improved runtime device management
- The runtime now defaults to attempting context creation on other
devices in the system before returning any failure messages. The new
call cudaSetValidDevices() allows the application to specify a list of
acceptable devices for use.
- cudaSetValidDevices
o Driver/runtime version query functions
- Applications can now directly query version information about the
underlying driver/runtime.
- cuDriverGetVersion
- cudaDriverGetVersion
- cudaRuntimeGetVersion
o New device attribute queries
- CU_DEVICE_ATTRIBUTE_INTEGRATED
- CU_DEVICE_ATTRIBUTE_CAN_MAP_HOST_MEMORY
- CU_DEVICE_ATTRIBUTE_COMPUTE_MODE
Documentation
o Doxygen-generated and cross-referenced html, pdf, and man pages.
- Runtime API
- Driver API