From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dts@dpdk.org, dev@dpdk.org
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: [dpdk-dev] Userspace testing
Date: Wed, 29 Jul 2020 10:34:34 -0400 [thread overview]
Message-ID: <CAHx6DYBhdOzZRbvMUBLDCbfbsuffgqgWAHstvyD1HmP=sj4tGA@mail.gmail.com> (raw)
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
next reply other threads:[~2020-07-29 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 14:34 Owen Hilyard [this message]
2020-07-29 15:35 ` Burakov, Anatoly
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:
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='CAHx6DYBhdOzZRbvMUBLDCbfbsuffgqgWAHstvyD1HmP=sj4tGA@mail.gmail.com' \
--to=ohilyard@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
--cc=lylavoie@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
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).