From: Bruce Richardson <bruce.richardson@intel.com>
To: Dave Young <dave@youngcopy.com>
Cc: <dev@dpdk.org>, Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH v3 5/7] Section 5: Appendix
Date: Fri, 17 Nov 2023 13:04:48 +0000 [thread overview]
Message-ID: <ZVdk8Encw/epIXEq@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAMXm8ERQDweYFP03i71vinTgQswVYYgvjrzMu2KWJt_7Ajkguw@mail.gmail.com>
On Wed, Nov 15, 2023 at 08:28:55PM -0500, Dave Young wrote:
> Bruce,
> Is the following Linux update correct per your feedback?
> Linux
> -----
> To run DPDK applications without root privileges on Linux, perform the
> following steps:
> 1. **Create a DPDK User Group**: Create a new user group for DPDK and
> add the desired user to this group.
> 2. **Set Up Hugepages**: Configure hugepages for the user.
> 3. **Bind the NIC to a User-Space Driver**: Use the DPDK tool
> ``dpdk-devbind.py`` to bind the NIC to a user-space driver like
> ``vfio-pci`` or ``igb_uio``
These three steps don't need to be covered in the docs. We already
described elsewhere about configuring hugepages and binding the device.
Also, to run as non-root, I would expect there to be a user a/c already
available on the system that the deployer of the app wants to use.
> 4. **Adjust Permissions for Specific Files and Directories**:
>
> - VFIO entries in ``/dev``, such as ``/dev/vfio/<id>``, where <id>
> is the VFIO group to which a device used by DPDK belongs.
> - The hugepage mount directory, typically ``/dev/hugepages`` on many
> distributions, or any alternative mount point configured by the user,
> e.g., ``/mnt/huge``, ``/mnt/huge_1G``.
> Note: Running DPDK as non-root on Linux requires IOMMU support
> through vfio.
This note needs to be explicitly called out to the top of the instructions.
The list of files to change the permissions on is key. The action -
changing permissions - is common between Linux and BSD, but the specific
files to adjust will be different.
> 5. **Run the DPDK Application**: Run the desired DPDK application as
> the user who has been added to the DPDK group.
> FreeBSD
> -------
> - The userspace-io device files in ``/dev``, for example,
> ``/dev/uio0``, ``/dev/uio1``, and so on
> - The userspace contiguous memory device: ``/dev/contigmem``
Regards,
/Bruce
next prev parent reply other threads:[~2023-11-17 13:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 4:01 [PATCH v3 0/7] docs: getting started guide consolidation David Young
2023-11-03 4:01 ` [PATCH v3 1/7] Section 1: Introduction David Young
2023-11-03 13:11 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 2/7] Section 2: Install and Build DPDK David Young
2023-11-03 13:55 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 3/7] Section 3: Setting up a System to Run DPDK Applications David Young
2023-11-03 14:17 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 4/7] Section 4: Running Applications David Young
2023-11-03 15:13 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 5/7] Section 5: Appendix David Young
2023-11-03 15:23 ` Bruce Richardson
2023-11-16 1:28 ` Dave Young
2023-11-17 13:04 ` Bruce Richardson [this message]
2023-11-03 4:01 ` [PATCH v3 6/7] Added link to Getting Started Guide in index.rst David Young
2023-11-03 13:32 ` Bruce Richardson
2023-11-03 14:22 ` Bruce Richardson
2023-11-08 1:47 ` Dave Young
2023-11-08 2:06 ` Dave Young
2023-11-03 4:01 ` [PATCH v3 7/7] Section 6: Glossary David Young
2023-11-03 15:26 ` Bruce Richardson
2023-11-23 1:26 ` [PATCH v4 0/6] docs: getting started guide consolidation David Young
2023-11-23 1:26 ` [PATCH v4 1/6] Section 1: Introduction David Young
2023-11-23 1:26 ` [PATCH v4 2/6] Section 2: Install and Build DPDK David Young
2023-11-23 1:26 ` [PATCH v4 3/6] Section 3: Setting up a System to Run DPDK Applications David Young
2023-11-23 1:26 ` [PATCH v4 4/6] Section 4: Running Applications David Young
2023-11-23 1:26 ` [PATCH v4 5/6] Section 5: Appendix David Young
2023-11-23 1:26 ` [PATCH v4 6/6] Section 6: Glossary David Young
2023-12-01 15:17 ` [PATCH v4 0/6] docs: getting started guide consolidation 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=ZVdk8Encw/epIXEq@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aconole@redhat.com \
--cc=dave@youngcopy.com \
--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).