* [dpdk-dev] rte APIs for allocating IOVA contiguous memory
@ 2020-09-18 7:49 Devendra Singh Rawat
0 siblings, 0 replies; only message in thread
From: Devendra Singh Rawat @ 2020-09-18 7:49 UTC (permalink / raw)
Apart from using rte_memzone_reserve_* APIs, is there any other way to allocate IOVA contiguous memory block in DPDK ?
If I am correct there is no 'rte' API to allocate an anonymous IOVA contiguous memory block from a heap, right ?
My PMD needs to allocate many IOVA contiguous memory blocks of different sizes according to parameters passed to DPDK application.
These blocks are shared by PMD and HW.
I can't use mempool as block size is not fixed.
I can't use rte_memzone_reserve_* either as I am hitting RTE_MAX_MEMZONE limit, and setting this limit to a higher value is not an option for me.
I also can't enforce the policies of using legacy memory model, and IOMMU in VA mode.
I can see rte_malloc_socket() but it does not provide any provision to pass RTE_MEMZONE_IOVA_CONTIG flag to
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-18 7:49 [dpdk-dev] rte APIs for allocating IOVA contiguous memory Devendra Singh Rawat
DPDK patches and discussions
Archives are clonable:
git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/ public-inbox