DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Owen Hilyard <ohilyard@iol.unh.edu>, dts@dpdk.org, dev@dpdk.org
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: Re: [dpdk-dev] Userspace testing
Date: Wed, 29 Jul 2020 16:35:20 +0100
Message-ID: <c70020a2-8948-dda4-bf1f-f5c29ec151b1@intel.com> (raw)
In-Reply-To: <CAHx6DYBhdOzZRbvMUBLDCbfbsuffgqgWAHstvyD1HmP=sj4tGA@mail.gmail.com>

On 29-Jul-20 3:34 PM, Owen Hilyard wrote:
> Hello all,
> I was wondering what everyone's thoughts on doing both userspace testing
> and unprivileged testing of dpdk applications is. DTS currently runs all
> commands on the tester and the dut as the root user. Please correct me if
> I'm wrong, but I was under the assumption that most applications written
> with dpdk would not run as root. This could present a problem since it is
> possible that permissions errors could arise and we wouldn't notice it due
> to the way we currently test. Given that, I was wondering what should and
> should not be possible as a normal (non-root) user, and what would be the
> best way to go about verifying this.
> Thanks

This is useful, but not everything is supposed to work with limited 
privileges. Things that definitely *won't* work are KNI and anything 
igb_uio-related. Everything VFIO should work fine, and setting up 
correct permissions for hugepages and VFIO is one of the trickier things 
that even I don't know how to do correctly off the top of my head :D

An easy stopgap way of running almost everything as an unprivileged user 
is to use in-memory mode (--in-memory EAL switch); this will cause EAL 
to reserve hugepages etc. without touching the filesystem, sacrificing 
secondary process support in the process (so e.g. EAL autotest won't 
work in --in-memory mode as it relies on secondary process support).

So, i would say that it would be a valuable thing to test for, but be 
aware that not everything is expected to work.


  reply	other threads:[~2020-07-29 15:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 14:34 Owen Hilyard
2020-07-29 15:35 ` Burakov, Anatoly [this message]
2020-07-30 16:54   ` Owen Hilyard
2020-07-31  9:12     ` Burakov, Anatoly
2020-08-03 14:31       ` Owen Hilyard
2020-08-10  8:53         ` Burakov, Anatoly
2020-07-31  7:43 ` David Marchand

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c70020a2-8948-dda4-bf1f-f5c29ec151b1@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    --cc=ohilyard@iol.unh.edu \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git