# Why is there no \`cudaMallocArrayAsync\`?

**URL:** <https://forums.developer.nvidia.com/t/why-is-there-no-cudamallocarrayasync/330258>\
**Category:** CUDA Programming and Performance\
**Tags:** cuda\
**Created:** [April 14, 2025, 12:18pm UTC](https://forums.developer.nvidia.com/t/why-is-there-no-cudamallocarrayasync/330258 "2025-04-14T12:18:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Robert\_Crovella](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/robert_crovella/32/14043_2.png) [@Robert\_Crovella](https://forums.developer.nvidia.com/u/Robert_Crovella)\
**Post date:** [April 14, 2025, 2:19pm UTC](https://forums.developer.nvidia.com/t/why-is-there-no-cudamallocarrayasync/330258/2 "2025-04-14T14:19:15Z")

</div>

> [@matias.christensen](#):
>
> As far as I know, memory allocated with `cudaMallocArray` isn’t inherently special or stored in some special way.

There must be something special about it. If there were not, the CUDA designers presumably would have just used `cudaMalloc` for underlying array allocations.

I’m not aware of any method to provide an underlying allocation for a `cudaArray` other than `cudaMallocArray` and its similar cousins.

AFAIK the reason why is not documented by NVIDIA.

If you’d like to see a change in CUDA or its documentation, one possibility is to [file a bug](https://forums.developer.nvidia.com/t/how-to-report-a-bug/67911).

---

_[View the full topic](https://forums.developer.nvidia.com/t/why-is-there-no-cudamallocarrayasync/330258)._