From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 893] no_hugetlbfs should not mean legacy_mem on iommu/vfio platforms
Date: Fri, 03 Dec 2021 02:17:40 +0000 [thread overview]
Message-ID: <bug-893-3@http.bugs.dpdk.org/> (raw)
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@dpdk.org
Reporter: niketkandya@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.
reply other threads:[~2021-12-03 2:17 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=bug-893-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).