DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Owen Hilyard <ohilyard@iol.unh.edu>
Cc: dts@dpdk.org, dev@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: Re: [dpdk-dev] Userspace testing
Date: Fri, 31 Jul 2020 10:12:39 +0100
Message-ID: <bbd7d9a1-09bc-3fc8-b9f1-ab9c71e6c113@intel.com> (raw)
In-Reply-To: <CAHx6DYDJGareBnmajrR6wZE=w0QhyQTn1XQ1boq=No0fnGdWUQ@mail.gmail.com>

On 30-Jul-20 5:54 PM, Owen Hilyard wrote:
> Thanks for the advice.
> 
> I was wondering about the state of the "Setup VFIO permissions" option 
> in the setup script. It seems to just modify the character device's 
> permissions and then check their memory limit. Should this option also 
> handle the hugepages setup?

I was under the (mis?)impression that the hugepage setup part of the 
script did that?

> 
> Thanks
> 
> On Wed, Jul 29, 2020 at 11:35 AM Burakov, Anatoly 
> <anatoly.burakov@intel.com <mailto:anatoly.burakov@intel.com>> wrote:
> 
>     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.
> 
>     -- 
>     Thanks,
>     Anatoly
> 


-- 
Thanks,
Anatoly

  reply	other threads:[~2020-07-31  9:12 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
2020-07-30 16:54   ` Owen Hilyard
2020-07-31  9:12     ` Burakov, Anatoly [this message]
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:
  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=bbd7d9a1-09bc-3fc8-b9f1-ab9c71e6c113@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 \
    /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

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 \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


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