From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 118] conflicting information for 'Running DPDK Applications Without Root Privileges'
Date: Wed, 05 Dec 2018 05:43:23 +0000 [thread overview]
Message-ID: <bug-118-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=118
Bug ID: 118
Summary: conflicting information for 'Running DPDK Applications
Without Root Privileges'
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: doc
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
link 1:
http://doc.dpdk.org/guides/freebsd_gsg/build_sample_apps.html?highlight=without%20root
statement: 'with a number of small permission adjustments, it is possible to
run these applications as a user other than “root”. '
link 2:
http://doc.dpdk.org/guides/linux_gsg/enable_func.html?highlight=without%20root
statement: since version 4.0, the kernel does not allow unprivileged processes
to read the physical address information from the pagemaps file, making it
impossible for those processes to use HW devices which require physical
addresses
Can we either have 1 link for this or update both place with kernel 4.0 issue.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-12-05 5:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-118-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).