Skip to content

Conversation

@Wangl56
Copy link

@Wangl56 Wangl56 commented Dec 4, 2025

This change is to expose the below APIs to user to let users be able to leverage them to map the user allocated memory to iova address and configure it to qat dma engine to avoid none-necessary memory copy when qat engine transfer data to user memory.
iova_release -> qae_iova_release
allocate_iova -> qae_allocate_iova
dma_map_slab -> qae_dma_map_slab
dma_unmap_slab -> qae_dma_unmap_slab

This change is to expose the below APIs to user to let users be able to
leverage them to map the user allocated memory to iova address and
configure it to qat dma engine to avoid none-necessary memory copy when
qat engine transfer data to user memory.
iova_release  -> qae_iova_release
allocate_iova -> qae_allocate_iova
dma_map_slab  -> qae_dma_map_slab
dma_unmap_slab -> qae_dma_unmap_slab
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant