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: Mon, 10 Aug 2020 09:53:05 +0100 [thread overview]
Message-ID: <1f3a3a2f-fa0d-2f89-a40d-429a1f1be69d@intel.com> (raw)
In-Reply-To: <CAHx6DYBNEwNrTcbEXOv6ifOTbTu0cGrE8jW9-G5QCfdHSotJ_g@mail.gmail.com>
On 03-Aug-20 3:31 PM, Owen Hilyard wrote:
>
>
> On Fri, Jul 31, 2020 at 5:12 AM Burakov, Anatoly
> <anatoly.burakov@intel.com <mailto:anatoly.burakov@intel.com>> wrote:
>
> 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?
>
> It doesn't appear to set them up so that non-root users can use them.
> From what I can tell it only creates the pages, but doesn't change
> permissions on them in any way.
Right. Then, it probably should (or perhaps it should be added as
another menu option, as probably not everyone would want to do a
chmod/chown on hugepage mounts).
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-08-10 8:53 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
2020-08-03 14:31 ` Owen Hilyard
2020-08-10 8:53 ` Burakov, Anatoly [this message]
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=1f3a3a2f-fa0d-2f89-a40d-429a1f1be69d@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
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).