Shuenhoy/vtk-m
1
0
Fork 0
mirror of https://gitlab.kitware.com/vtk/vtk-m synced 2024-09-08 13:23:51 +00:00
Code Issues 2 Actions Packages Projects Releases Wiki Activity
81522be6f7
vtk-m/vtkm/cont/cuda/DeviceAdapterCuda.h

38 lines
1.3 KiB
C
Raw Normal View History

Adding a cuda device adapter to vtkm. Porting the dax device adapter over to vtkm. Unlike the dax version, doesn't use the thrust::device_vector, but instead uses thrust::system calls so that we can support multiple thrust based backends. Also this has Texture Memory support for input array handles. Some more work will need to be done to ArrayHandle so that everything works when using an ArrayHandle inplace with texture memory bindings.
2014-11-26 17:19:46 +00:00
//============================================================================
// Copyright (c) Kitware, Inc.
// All rights reserved.
// See LICENSE.txt for details.
conslidate the license statement
2019-04-15 23:24:21 +00:00
//
Adding a cuda device adapter to vtkm. Porting the dax device adapter over to vtkm. Unlike the dax version, doesn't use the thrust::device_vector, but instead uses thrust::system calls so that we can support multiple thrust based backends. Also this has Texture Memory support for input array handles. Some more work will need to be done to ArrayHandle so that everything works when using an ArrayHandle inplace with texture memory bindings.
2014-11-26 17:19:46 +00:00
// This software is distributed WITHOUT ANY WARRANTY; without even
// the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
// PURPOSE. See the above copyright notice for more information.
//============================================================================
#ifndef vtk_m_cont_cuda_DeviceAdapterCuda_h
#define vtk_m_cont_cuda_DeviceAdapterCuda_h
#include <vtkm/cont/cuda/internal/DeviceAdapterTagCuda.h>
DeviceAdapter Tags now always exist, and contain if the device is valid. Previously it was really hard to verify if a device adapter was valid. Since you would have to check for the existence of the tag. Now the tag always exists, but instead you query the traits of the DeviceAdapter to see if it is a valid adapter. This makes compiling with multiple backends alot easier.
2015-09-16 20:59:28 +00:00
Replace basic ArrayHandle implementation to use Buffers This encapsulates a lot of the required memory management into the Buffer object and related code. Many now unneeded classes were deleted.
2020-04-22 19:58:59 +00:00
#ifdef VTKM_ENABLE_CUDA
Make cuda DeviceAdapter valid only when using nvcc Before it was valid even on a regular compiler, if cuda was available.
2015-09-18 15:51:41 +00:00
#ifdef VTKM_CUDA
Workaround inclusive_scan issues in thrust 1.8.X for complex value types. The original workaround for inclusive_scan bugs in thrust 1.8 only solved the issue for basic arithmetic types such as int, float, double. Now we go one step further and fix the problem for all types. The solution is to provide a proper implementation of destructive_accumulate_n and make sure it exists before any includes of thrust occur.
2015-11-09 15:31:51 +00:00
//This is required to be first so that we get patches for thrust included
//in the correct order
#include <vtkm/exec/cuda/internal/ThrustPatches.h>
Adding a cuda device adapter to vtkm. Porting the dax device adapter over to vtkm. Unlike the dax version, doesn't use the thrust::device_vector, but instead uses thrust::system calls so that we can support multiple thrust based backends. Also this has Texture Memory support for input array handles. Some more work will need to be done to ArrayHandle so that everything works when using an ArrayHandle inplace with texture memory bindings.
2014-11-26 17:19:46 +00:00
#include <vtkm/cont/cuda/internal/DeviceAdapterAlgorithmCuda.h>
Add Buffer class The buffer class encapsulates the movement of raw C arrays between host and devices. The `Buffer` class itself is not associated with any device. Instead, `Buffer` is used in conjunction with a new templated class named `DeviceAdapterMemoryManager` that can allocate data on a given device and transfer data as necessary. `DeviceAdapterMemoryManager` will eventually replace the more complicated device adapter classes that manage data on a device. The code in `DeviceAdapterMemoryManager` is actually enclosed in virtual methods. This allows us to limit the number of classes that need to be compiled for a device. Rather, the implementation of `DeviceAdapterMemoryManager` is compiled once with whatever compiler is necessary, and then the `RuntimeDeviceInformation` is used to get the correct object instance.
2020-03-26 23:34:18 +00:00
#include <vtkm/cont/cuda/internal/DeviceAdapterMemoryManagerCuda.h>
Implement RuntimeDeviceConfiguration
2021-05-26 19:43:36 +00:00
#include <vtkm/cont/cuda/internal/RuntimeDeviceConfigurationCuda.h>
Replace basic ArrayHandle implementation to use Buffers This encapsulates a lot of the required memory management into the Buffer object and related code. Many now unneeded classes were deleted.
2020-04-22 19:58:59 +00:00
#else // !VTKM_CUDA
#ifndef VTKM_NO_ERROR_ON_MIXED_CUDA_CXX_TAG
#error When VTK-m is built with CUDA enabled all compilation units that include DeviceAdapterTagCuda must use the cuda compiler
#endif //!VTKM_NO_ERROR_ON_MIXED_CUDA_CXX_TAG
#endif // !VTKM_CUDA
#endif // VTKM_ENABLE_CUDA
Adding a cuda device adapter to vtkm. Porting the dax device adapter over to vtkm. Unlike the dax version, doesn't use the thrust::device_vector, but instead uses thrust::system calls so that we can support multiple thrust based backends. Also this has Texture Memory support for input array handles. Some more work will need to be done to ArrayHandle so that everything works when using an ArrayHandle inplace with texture memory bindings.
2014-11-26 17:19:46 +00:00
#endif //vtk_m_cont_cuda_DeviceAdapterCuda_h
Reference in New Issue Copy Permalink