From: "Wiles, Keith" <keith.wiles@intel.com>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Running DPDK as non-root
Date: Fri, 19 Aug 2016 18:39:28 +0000 [thread overview]
Message-ID: <7887A61A-F887-4BCD-941E-02C50963E89B@intel.com> (raw)
In-Reply-To: <CAGXJAmxWoJtb30Xd1CV86mYZMVU8MKuoOPxC4Uqf6uhG-z2MiQ@mail.gmail.com>
Regards,
Keith
> On Aug 19, 2016, at 1:16 PM, John Ousterhout <ouster@cs.stanford.edu> wrote:
>
> I'm trying to run a DPDK application as a normal user without root
> privilege, and saw the instructions here:
>
> http://dpdk.org/doc/guides/linux_gsg/enable_func.html
>
> However, when I try this I get the following log messages:
>
> EAL: Detected 8 lcore(s)
> EAL: Probing VFIO support...
> EAL: Cannot open /proc/self/pagemap: Operation not permitted. virt2phys
> address translation will not work
> PANIC in rte_eal_init():
> Cannot init memory
>
> I tried to change the permissions on /proc/self/pagemap, but that is
> disallowed, even if I try it as root.
>
> Any suggestions on how to get around this problem?
I have tried a couple times to make this happen for my development, but without any luck.
I believe one of the big problems is related the virt2phy address translation is done in the kernel and it is seen as a security hole if a user level application is able to access that information.
>
> Thanks in advance for the help.
>
> -John-
next prev parent reply other threads:[~2016-08-19 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 18:16 John Ousterhout
2016-08-19 18:39 ` Wiles, Keith [this message]
2016-08-25 13:56 ` Vincent JARDIN
-- strict thread matches above, loose matches on Subject: below --
2016-07-07 15:47 Jez Higgins
2016-07-07 16:17 ` Thomas Monjalon
2016-07-07 18:37 ` Wiles, Keith
2016-07-08 2:29 ` Tan, Jianfeng
2016-07-12 17:09 ` Adrien Mazarguil
2016-07-08 3:55 ` Singh, Satish 1. (Nokia - IN/Bangalore)
2016-07-08 5:01 ` Singh, Satish 1. (Nokia - IN/Bangalore)
2016-07-11 10:41 ` Jez Higgins
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=7887A61A-F887-4BCD-941E-02C50963E89B@intel.com \
--to=keith.wiles@intel.com \
--cc=ouster@cs.stanford.edu \
--cc=users@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).