DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kamaraj P <pkamaraj@gmail.com>
To: dev@dpdk.org
Cc: ksimha@cisco.com, kalas@cisco.com, seveluch@cisco.com
Subject: Re: [dpdk-dev] Running DPDK application with non-previlege mode
Date: Mon, 30 Aug 2021 13:22:11 +0530	[thread overview]
Message-ID: <CAG8PAap3obzE8qXyDX9-LdPo5k20eE3XNSHMyOOCCGxeGwFL2Q@mail.gmail.com> (raw)
In-Reply-To: <CAG8PAarTj04Mywxf3ZQbHLkqb0sw0TqMTr_ndx6OgKcZqtu_Hw@mail.gmail.com>

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.

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
>

  reply	other threads:[~2021-08-30  7:52 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 ` Kamaraj P [this message]
2021-08-30  8:37   ` [dpdk-dev] Running DPDK application with " Kamaraj P
2021-08-30 11:26   ` Ferruh Yigit
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=CAG8PAap3obzE8qXyDX9-LdPo5k20eE3XNSHMyOOCCGxeGwFL2Q@mail.gmail.com \
    --to=pkamaraj@gmail.com \
    --cc=dev@dpdk.org \
    --cc=kalas@cisco.com \
    --cc=ksimha@cisco.com \
    --cc=seveluch@cisco.com \
    /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).