Reference the common guide for generic setup.
Remove excessive capabilities from the recommended list.
Cc: sta...@dpdk.org
Signed-off-by: Dmitry Kozlyuk <dkozl...@nvidia.com>
---
doc/guides/platform/mlx5.rst | 22 ++++++++++------------
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git a/doc/guides/platform/mlx5.rst b/doc/guides/platform/mlx5.rst
index 64a4c5e76e..956a72fadf 100644
--- a/doc/guides/platform/mlx5.rst
+++ b/doc/guides/platform/mlx5.rst
@@ -404,25 +404,23 @@ The device can be bound again at this point.
Run as Non-Root
^^^^^^^^^^^^^^^
-In order to run as a non-root user,
-some capabilities must be granted to the application::
+Hugepage and resource limit setup is documented
+in the :ref:`common Linux guide <Running_Without_Root_Privileges>`.
+This PMD does not require physical addresses,
+so capability configuration is not needed to access hugepages.
+Note that physical addresses may be required by other drivers.
- setcap cap_sys_admin,cap_net_admin,cap_net_raw,cap_ipc_lock+ep <dpdk-app>
+Additional capabilities must be granted to the application::
-Below are the reasons for the need of each capability:
-
-``cap_sys_admin``
- When using physical addresses (PA mode), with Linux >= 4.0,
- for access to ``/proc/self/pagemap``.
+ setcap cap_net_raw,cap_net_admin,cap_sys_rawio+ep <executable>
-``cap_net_admin``
- For device configuration.
+Below are the reasons for the need of each capability:
``cap_net_raw``
For raw ethernet queue allocation through kernel driver.
-``cap_ipc_lock``
- For DMA memory pinning.
+``cap_net_admin``
+ For device configuration, like setting link status or MTU.
Windows Environment
--
2.25.1
