From: Devendra Singh Rawat <dsinghrawat@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] rte APIs for allocating IOVA contiguous memory
Date: Fri, 18 Sep 2020 07:49:51 +0000 [thread overview]
Message-ID: <CY4PR18MB14969307F550AE11C02476EBB63F0@CY4PR18MB1496.namprd18.prod.outlook.com> (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
malloc_heap_alloc().
Thanks,
Devendra
reply other threads:[~2020-09-18 7:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CY4PR18MB14969307F550AE11C02476EBB63F0@CY4PR18MB1496.namprd18.prod.outlook.com \
--to=dsinghrawat@marvell.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).