Skip to contentSkip to conversation

doc: expand description of no-huge and PMD issue

PATCH In review Stanislaw Kardach 3 participants 5 messages Jun 9, 2022 – Mar 31, 2023

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 doc: expand description of no-huge and PMD issue

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.

---
 doc/guides/rel_notes/known_issues.rst | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)
doc/guides/rel_notes/known_issues.rst +7 -3
index 570550843a..2e0ffbdd93 100644
@@ -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.
Signature · 1 line
2.30.2
#1 lore raw
Quoted 7 lines · Stanislaw Kardach

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.

Anatoly, Dmitry, opinions?
Thanks.

Signature · 1 line
David Marchand
#2 lore raw

13/06/2022 11:31, David Marchand:

Quoted 11 lines · Stanislaw Kardach
Quoted 7 lines

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.

Anatoly, Dmitry, opinions?
Thanks.

Why nobody is reviewing doc?

#3 lore raw

Ping for review

11/07/2022 23:09, Thomas Monjalon:

Quoted 14 lines

13/06/2022 11:31, David Marchand:

Quoted 11 lines · Stanislaw Kardach
Quoted 7 lines

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.

Anatoly, Dmitry, opinions?
Thanks.

Why nobody is reviewing doc?

#4 lore raw

15/11/2022 16:37, Thomas Monjalon:

Quoted 17 lines

Ping for review

11/07/2022 23:09, Thomas Monjalon:

Quoted 14 lines

13/06/2022 11:31, David Marchand:

Quoted 11 lines · Stanislaw Kardach
Quoted 7 lines

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.

Anatoly, Dmitry, opinions?
Thanks.

Why nobody is reviewing doc?

Applied without review.