[ET Device Support] CudaAllocator: device memory allocator for CUDA backend#18477
[ET Device Support] CudaAllocator: device memory allocator for CUDA backend#18477Gasoonjia wants to merge 1 commit intogh/gasoonjia/157/basefrom
Conversation
…ackend Implement CudaAllocator, a concrete DeviceAllocator using cudaMalloc/ cudaFree/cudaMemcpy for CUDA device memory management. The allocator is automatically registered with the DeviceAllocatorRegistry when the CUDA backend library is linked, ensuring DeviceMemoryBuffer::create(CUDA) works transparently. Differential Revision: [D98014184](https://our.internmc.facebook.com/intern/diff/D98014184/) [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/18477
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 Awaiting Approval, 162 New Failures, 3 Unrelated FailuresAs of commit 0fcfa83 with merge base 45a9717 ( AWAITING APPROVAL - The following workflows need approval before CI can run:
NEW FAILURES - The following jobs have failed:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
…ackend Implement CudaAllocator, a concrete DeviceAllocator using cudaMalloc/ cudaFree/cudaMemcpy for CUDA device memory management. The allocator is automatically registered with the DeviceAllocatorRegistry when the CUDA backend library is linked, ensuring DeviceMemoryBuffer::create(CUDA) works transparently. Differential Revision: [D98014184](https://our.internmc.facebook.com/intern/diff/D98014184/) ghstack-source-id: 357086933 Pull Request resolved: #18477
This PR needs a
|
Stack from ghstack (oldest at bottom):
Implement CudaAllocator, a concrete DeviceAllocator using cudaMalloc/ cudaFree/cudaMemcpy for CUDA device memory management. The allocator is automatically registered with the DeviceAllocatorRegistry when the CUDA backend library is linked, ensuring DeviceMemoryBuffer::create(CUDA) works transparently.
Differential Revision: D98014184