From: Raslan Darawsheh <rasland@mellanox.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Adrian Chiris <adrianc@mellanox.com>,
Moshe Levi <moshele@mellanox.com>,
Matan Azrad <matan@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add required Linux capabilities in mlx5 guide
Date: Thu, 14 May 2020 08:23:37 +0000 [thread overview]
Message-ID: <AM0PR05MB6707CF04367790B53E19FA93C2BC0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200302230853.1628014-1-thomas@monjalon.net>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Tuesday, March 3, 2020 1:09 AM
> To: dev@dpdk.org
> Cc: Adrian Chiris <adrianc@mellanox.com>; Moshe Levi
> <moshele@mellanox.com>; Matan Azrad <matan@mellanox.com>; Shahaf
> Shuler <shahafs@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; John McNamara
> <john.mcnamara@intel.com>; Marko Kovacevic
> <marko.kovacevic@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: add required Linux capabilities in mlx5
> guide
>
> If running DPDK as non-root, some extra capabilities may be required.
> The Mellanox devices, using a bifurcated model with Linux drivers,
> have some specific requirements summarized in mlx5 PMD guide.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Reviewed-by: Raslan Darwsheh <rasland@mellanox.com>
> ---
> doc/guides/nics/mlx5.rst | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index afd11cd830..7650e57dd0 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -359,6 +359,32 @@ Run-time configuration
>
> - **ethtool** operations on related kernel interfaces also affect the PMD.
>
> +Run as non-root
> +^^^^^^^^^^^^^^^
> +
> +In order to run as a non-root user,
> +some capabilities must be granted to the application::
> +
> + setcap cap_sys_admin,cap_net_admin,cap_net_raw,cap_ipc_lock+ep
> <dpdk-app>
> +
> +Below are the reasons of the need for each capability:
> +
> +``cap_sys_admin``
> + When using physical addresses (PA mode), with Linux >= 4.0,
> + for access to ``/proc/self/pagemap``.
> +
> +``cap_net_admin``
> + For MTU and link state modifications.
> +
> +``cap_net_raw``
> + For raw ethernet queue allocation through kernel driver.
> +
> +``cap_ipc_lock``
> + For DMA memory pinning.
> +
> +Driver options
> +^^^^^^^^^^^^^^
> +
> - ``rxq_cqe_comp_en`` parameter [int]
>
> A nonzero value enables the compression of CQE on RX side. This feature
> --
> 2.25.1
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2020-05-14 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 23:08 Thomas Monjalon
2020-05-14 8:23 ` Raslan Darawsheh [this message]
2020-05-14 17:29 ` Moshe Levi
2020-05-19 9:05 ` 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=AM0PR05MB6707CF04367790B53E19FA93C2BC0@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=adrianc@mellanox.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=matan@mellanox.com \
--cc=moshele@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@mellanox.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).