From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1631] PMD does not work with –no-huge EAL command line parameter
Date: Mon, 03 Feb 2025 02:46:47 +0000 [thread overview]
Message-ID: <bug-1631-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1631
Bug ID: 1631
Summary: PMD does not work with –no-huge EAL command line
parameter
Product: DPDK
Version: unspecified
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: nandinipersad361@gmail.com
Target Milestone: ---
Currently, the DPDK does not store any information about memory allocated by
malloc() (for example, NUMA node, physical address), hence PMDs do not work
when the --no-huge command line parameter is supplied to EAL. This happens when
using non-IOMMU based UIO drivers (i.e. igb_uio or uio_pci_generic) or when
IOVA mode is explicitly set to use physical addresses (via the --iova-mode=pa
EAL parameter).
Implication:
Sending and receiving data with PMD will not work. Unit tests checking
--no-huge operation will fail if there is a device bound to the PMD
(eal_flags_n_opt_autotest, eal_flags_no_huge_autotest,
eal_flags_vdev_opt_autotest, eal_flags_misc_autotest).
Resolution/Workaround:
Use huge page memory or use VFIO to map devices.
Affected Environment/Platform:
Systems running the DPDK on Linux
Driver/Module:
Poll Mode Driver (PMD).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3323 bytes --]
reply other threads:[~2025-02-03 2:46 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-1631-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.