Removes MemPoolContext from custom user mempools. The ground truth for which pool should be used is in graph_pools active pool, and MemPoolContext just introduced an opportunity for the pool pointed to by MemPoolContext and active pool in graph_pools to go out of sync (see all the asserts in the code to make sure that happens, and yet it still could happen in a multithread scenario, see my recent PRs (#153990). Pull Request resolved: https://github.com/pytorch/pytorch/pull/154042 Approved by: https://github.com/albanD, https://github.com/syed-ahmed |
||
|---|---|---|
| .. | ||
| impl | ||
| test | ||
| BUILD.bazel | ||
| build.bzl | ||
| CMakeLists.txt | ||
| CUDAAlgorithm.h | ||
| CUDAAllocatorConfig.cpp | ||
| CUDAAllocatorConfig.h | ||
| CUDACachingAllocator.cpp | ||
| CUDACachingAllocator.h | ||
| CUDADeviceAssertion.h | ||
| CUDADeviceAssertionHost.cpp | ||
| CUDADeviceAssertionHost.h | ||
| CUDAException.cpp | ||
| CUDAException.h | ||
| CUDAFunctions.cpp | ||
| CUDAFunctions.h | ||
| CUDAGraphsC10Utils.h | ||
| CUDAGuard.h | ||
| CUDAMacros.h | ||
| CUDAMallocAsyncAllocator.cpp | ||
| CUDAMathCompat.h | ||
| CUDAMiscFunctions.cpp | ||
| CUDAMiscFunctions.h | ||
| CUDAStream.cpp | ||
| CUDAStream.h | ||
| driver_api.cpp | ||
| driver_api.h | ||
| README.md | ||
c10/cuda is a core library with CUDA functionality. It is distinguished from c10 in that it links against the CUDA library, but like c10 it doesn't contain any kernels, and consists solely of core functionality that is generally useful when writing CUDA code; for example, C++ wrappers for the CUDA C API.
Important notes for developers. If you want to add files or functionality to this folder, TAKE NOTE. The code in this folder is very special, because on our AMD GPU build, we transpile it into c10/hip to provide a ROCm environment. Thus, if you write:
// c10/cuda/CUDAFoo.h
namespace c10 { namespace cuda {
void my_func();
}}
this will get transpiled into:
// c10/hip/HIPFoo.h
namespace c10 { namespace hip {
void my_func();
}}
Thus, if you add new functionality to c10, you must also update C10_MAPPINGS
torch/utils/hipify/cuda_to_hip_mappings.py to transpile
occurrences of cuda::my_func to hip::my_func. (At the moment,
we do NOT have a catch all cuda:: to hip:: namespace conversion,
as not all cuda namespaces are converted to hip::, even though
c10's are.)
Transpilation inside this folder is controlled by CAFFE2_SPECIFIC_MAPPINGS
(oddly enough.) C10_MAPPINGS apply to ALL source files.
If you add a new directory to this folder, you MUST update both c10/cuda/CMakeLists.txt and c10/hip/CMakeLists.txt