DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Jez Higgins <jez@jezuk.co.uk>, "users@dpdk.org" <users@dpdk.org>,
	"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
	"Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
Subject: Re: [dpdk-users] Running DPDK as non-root
Date: Thu, 7 Jul 2016 18:37:39 +0000	[thread overview]
Message-ID: <F1CFD0D3-7315-4C3B-ACF0-BDF49F0D10A2@intel.com> (raw)
In-Reply-To: <4313092.zcSIIfa3F0@xps13>


> On Jul 7, 2016, at 11:17 AM, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> 
> Hi
> 
> 2016-07-07 16:47, Jez Higgins:
>> Is it possible to get DPDK up and running as non-root - if so, can
>> anyone guide me to what I'm missing? Or should I be giving this up as a
>> bad job?
> 
> You can try the --no-huge option.
> But most of drivers won't work without hugepage currently.
> A rework of the memory allocation is needed to make it work better.

Last time I looked DPDK must be run as root as the virtual to physical translation in the startup needs to be root, unless the no-huge option alters the requirement. As I understand the virtual to physical translation needing to be run a root is a Linux restriction. I do not know of any work arounds.

  reply	other threads:[~2016-07-07 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 15:47 Jez Higgins
2016-07-07 16:17 ` Thomas Monjalon
2016-07-07 18:37   ` Wiles, Keith [this message]
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
2016-08-19 18:16 John Ousterhout
2016-08-19 18:39 ` Wiles, Keith
2016-08-25 13:56 ` Vincent JARDIN

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=F1CFD0D3-7315-4C3B-ACF0-BDF49F0D10A2@intel.com \
    --to=keith.wiles@intel.com \
    --cc=jez@jezuk.co.uk \
    --cc=olivier.matz@6wind.com \
    --cc=sergio.gonzalez.monroy@intel.com \
    --cc=thomas.monjalon@6wind.com \
    --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).