From: David Christensen <drc@linux.vnet.ibm.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Permissions Required to Run DPDK/MLX5 as Non-Root User?
Date: Mon, 24 Feb 2020 14:38:38 -0800 [thread overview]
Message-ID: <3f84f815-61c4-a826-9850-7ca56946d3e8@linux.vnet.ibm.com> (raw)
In-Reply-To: <1e44afa0-951c-9161-75d9-a1f679a1995e@linux.vnet.ibm.com>
On 2/20/20 11:24 AM, David Christensen wrote:
> Running DPDK 20.02-rc3 and attempting to use the MLX5 PMD as a non-root
> user. When starting testpmd I'm receiving the following error on both
> Power and x86_64 platforms (full output further down):
>
> net_mlx5: probe of PCI device 0000:01:00.0 aborted after encountering
> an error: Operation not supported
Ended up with two answers:
1) Manually clean out /dev/hugepages. Often encountered root owned
files left over from previous test runs, causing memory allocation
failures when DPDK couldn't use the name it wanted (rtemap_*).
2) Needed to manually add special permissions to dpdk-testpmd (thanks
Shahaf):
# setcap cap_net_raw,cap_net_admin,cap_ipc_lock+eip
~/src/dpdk/build/app/dpdk-testpmd
Dave
prev parent reply other threads:[~2020-02-24 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 19:24 David Christensen
2020-02-24 22:38 ` David Christensen [this message]
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=3f84f815-61c4-a826-9850-7ca56946d3e8@linux.vnet.ibm.com \
--to=drc@linux.vnet.ibm.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).