From: Stanislaw Kardach <kda@semihalf.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Stanislaw Kardach <kda@semihalf.com>,
dev@dpdk.org, upstream@semihalf.com
Subject: [PATCH 1/1] doc: expand description of no-huge and PMD issue
Date: Thu, 9 Jun 2022 15:40:11 +0200 [thread overview]
Message-ID: <20220609134011.725343-1-kda@semihalf.com> (raw)
Add more details to the description of a known issue of PMDs not being
usable when --no-huge EAL command line parameter is used. The issue
actually happens whenever there is a need for physical addresses, even
when there is no PMD attached.
Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
---
doc/guides/rel_notes/known_issues.rst | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 570550843a..2e0ffbdd93 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -249,11 +249,15 @@ PMD does not work with --no-huge EAL command line parameter
-----------------------------------------------------------
**Description**:
- 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.
+ 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.
+ 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.
--
2.30.2
next reply other threads:[~2022-06-09 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 13:40 Stanislaw Kardach [this message]
2022-06-13 9:31 ` David Marchand
2022-07-11 21:09 ` Thomas Monjalon
2022-11-15 15:37 ` Thomas Monjalon
2023-03-31 10:07 ` Thomas Monjalon
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=20220609134011.725343-1-kda@semihalf.com \
--to=kda@semihalf.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=upstream@semihalf.com \
/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).