From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>, Kamaraj P <pkamaraj@gmail.com>
Cc: dev@dpdk.org, Anatoly Burakov <anatoly.burakov@intel.com>,
David Marchand <david.marchand@redhat.com>,
ksimha@cisco.com, kalas@cisco.com, seveluch@cisco.com,
"techboard@dpdk.org" <techboard@dpdk.org>,
hpai@cisco.com
Subject: Re: [dpdk-dev] Running DPDK application with non-previlege mode
Date: Mon, 30 Aug 2021 14:05:52 +0200 [thread overview]
Message-ID: <1827863.rKngybTHLR@thomas> (raw)
In-Reply-To: <CAG8PAaoD-z3BjbHfMyfnsRv9x6Rmeb0+kfV9sV-dDEMytu5qCg@mail.gmail.com>
30/08/2021 13:45, Kamaraj P:
> Thanks Ferruh.
> One more option which we have figured out to resolve this error by adding
> SYS_NICE capability ( --cap-add=NET_ADMIN --cap-add=SYS_RESOURCE
> --cap-add=SYS_NICE).
> Not sure whether it will work for all the scenarios. However the above
> options will ensure DPDK application can run as non-previlage mode ?
> Please suggest the right approach which should work for all the DPDK
> versions.
It depends on which device/driver you use.
Here are some infos:
`SYS_ADMIN`
Required for finding IOVA physical addresses.
Not needed if using virtual addressing (DPDK default)
or if Linux is older than 4.0.
`SYS_NICE`
Enable the syscalls `get_mempolicy` and `set_mempolicy`
required for NUMA memory management.
Not needed if `RTE_EAL_NUMA_AWARE_HUGEPAGES` is disabled
(explicitly or because of missing libnuma).
`SYS_RAWIO`
Enable the syscall `iopl` required for I/O port,
used for legacy virtio mode.
`NET_ADMIN`
Required for some device configuration.
`NET_RAW`
Required for mlx5 queue allocation. Enabled by default in Docker.
`IPC_LOCK`
Required for some DMA pinning.
next prev parent reply other threads:[~2021-08-30 12:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 7:37 [dpdk-dev] Running DPDK application without non-previlege mode Kamaraj P
2021-08-30 7:52 ` [dpdk-dev] Running DPDK application with " Kamaraj P
2021-08-30 8:37 ` Kamaraj P
2021-08-30 11:26 ` Ferruh Yigit
2021-08-30 11:45 ` Kamaraj P
2021-08-30 12:05 ` Thomas Monjalon [this message]
2021-08-30 11:59 ` Thomas Monjalon
2021-08-30 12:06 ` David Marchand
2021-08-31 15:27 ` Kamaraj P
2021-08-31 15:34 ` David Marchand
2021-08-31 16:20 ` Kamaraj P
2021-08-31 19:44 ` Bruce Richardson
2021-09-01 16:09 ` Kamaraj P
2021-09-01 17:52 ` Thomas Monjalon
2021-09-05 16:54 ` Kamaraj P
2021-09-06 14:02 ` Kamaraj P
2021-08-31 17:49 ` Aaron Conole
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=1827863.rKngybTHLR@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hpai@cisco.com \
--cc=kalas@cisco.com \
--cc=ksimha@cisco.com \
--cc=pkamaraj@gmail.com \
--cc=seveluch@cisco.com \
--cc=techboard@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.