[ET Device Support] CudaAllocator: device memory allocator for CUDA backend#18477
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. ❌ 3 New Failures, 1 Pending, 6 Unrelated Failures, 1 Unclassified FailureAs of commit f21f0b2 with merge base a83e7c4 ( NEW FAILURES - The following jobs have failed:
UNCLASSIFIED FAILURE - DrCI could not classify the following job because the workflow did not run on the merge base. The failure may be pre-existing on trunk or introduced by this PR:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
BROKEN TRUNK - The following jobs failed but was 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
|
… for CUDA backend" 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]
… for CUDA backend" 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]
digantdesai
left a comment
There was a problem hiding this comment.
Review automatically exported from Phabricator review in Meta.
… for CUDA backend" 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]
JacobSzwejbka
left a comment
There was a problem hiding this comment.
Review automatically exported from Phabricator review in Meta.
b0f2c9c
into
gh/gasoonjia/157/base
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