From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kamaraj P <pkamaraj@gmail.com>, <dev@dpdk.org>,
Anatoly Burakov <anatoly.burakov@intel.com>,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: <ksimha@cisco.com>, <kalas@cisco.com>, <seveluch@cisco.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] Running DPDK application with non-previlege mode
Date: Mon, 30 Aug 2021 12:26:48 +0100 [thread overview]
Message-ID: <66ba0b52-83bf-f7a0-aa79-66a267af32c4@intel.com> (raw)
In-Reply-To: <CAG8PAap3obzE8qXyDX9-LdPo5k20eE3XNSHMyOOCCGxeGwFL2Q@mail.gmail.com>
On 8/30/2021 8:52 AM, Kamaraj P wrote:
> Hello All,
> Some more info.
> We are using DPDK 19.11.
>
> When we bringup application with --security-opt seccomp=unconfined
> option..
> THe application bringup successfully and didnt observe any error when DPDK
> init logs.
> Will that --security-opt seccomp=unconfined option recommended for
> non-previlege mode for DPDK application ?
> Please suggest.
>
+ Anatoly, he may have experience on running on non-privilege mode.
Thomas, David,
What do you think documenting how to run as non root, we had similar question
before, if memory serves me right Red Hat was looking for same thing at some point.
If we are agree, perhaps we can find a volunteer in the tech board for it.
> Thanks,
> Kamaraj
>
> On Mon, Aug 30, 2021 at 1:07 PM Kamaraj P <pkamaraj@gmail.com> wrote:
>
>> Hello All,
>>
>> We are not able to run the DPDK allocation without using privilege option.
>>
>> Able to see the below erors:
>>
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> EAL: FATAL: rte_service_init() failed
>> Failed to init DPDK.set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> Failed to create mbuf for pool DPDK_POOL_0 frame_len=2048 num_mbufs=13824
>> ret (Exec format error)
>>
>> BTW we are also enabling --iova-mode=va option as part DPDK init.
>>
>> Can anyone please throw some light on this ?
>>
>> Thanks,
>> Kamaraj
>>
next prev parent reply other threads:[~2021-08-30 11:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 7:37 [dpdk-dev] Running DPDK application without " Kamaraj P
2021-08-30 7:52 ` [dpdk-dev] Running DPDK application with " Kamaraj P
2021-08-30 8:37 ` Kamaraj P
2021-08-30 11:26 ` Ferruh Yigit [this message]
2021-08-30 11:45 ` Kamaraj P
2021-08-30 12:05 ` Thomas Monjalon
2021-08-30 11:59 ` Thomas Monjalon
2021-08-30 12:06 ` David Marchand
2021-08-31 15:27 ` Kamaraj P
2021-08-31 15:34 ` David Marchand
2021-08-31 16:20 ` Kamaraj P
2021-08-31 19:44 ` Bruce Richardson
2021-09-01 16:09 ` Kamaraj P
2021-09-01 17:52 ` Thomas Monjalon
2021-09-05 16:54 ` Kamaraj P
2021-09-06 14:02 ` Kamaraj P
2021-08-31 17:49 ` Aaron Conole
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=66ba0b52-83bf-f7a0-aa79-66a267af32c4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=kalas@cisco.com \
--cc=ksimha@cisco.com \
--cc=pkamaraj@gmail.com \
--cc=seveluch@cisco.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
/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).