[Bug 893] no_hugetlbfs should not mean legacy_mem on iommu/vfio platforms
bugzilla at dpdk.org
bugzilla at dpdk.org
Fri Dec 3 03:17:40 CET 2021
https://bugs.dpdk.org/show_bug.cgi?id=893
Bug ID: 893
Summary: no_hugetlbfs should not mean legacy_mem on iommu/vfio
platforms
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev at dpdk.org
Reporter: niketkandya at google.com
Target Milestone: ---
>From my reading of the code and docs this is what I understand:
1. Huge pages are needed by DPDK so that user pages are always present and
pinned.
2. In systems with IOMMU and VFIO support, there should be no need for huge
pages. VFIO_IOMMU_MAP_DMA on any aligned buffer should do the same pinning.
--no-hugetlbfs today means that the system is also in --legacy-mem (which means
no dynamic allocation, 1 fixed heap of 64MB MEMSIZE_IF_NO_HUGE). I think this
is restrictive.
On systems with IOMMU/VFIO support --no-hugetlbfs should also support
dynamic(non legacy behavior) allocation.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the dev
mailing list