From: Kamaraj P <pkamaraj@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev <dev@dpdk.org>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
ksimha@cisco.com, kalas@cisco.com, seveluch@cisco.com,
"techboard@dpdk.org" <techboard@dpdk.org>,
hpai@cisco.com, ppitchai@cisco.com
Subject: Re: [dpdk-dev] Running DPDK application with non-previlege mode
Date: Tue, 31 Aug 2021 20:57:38 +0530 [thread overview]
Message-ID: <CAG8PAaqaGCh_2uJhK=DV9eU66wnyd-VkpL3r8uocOzcXRx+mwQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8x4y_JkN7i=uv1WCpXkK9qNc_R0=XnGKGKWMyRvRXLPVg@mail.gmail.com>
Hi Thomas,
We are trying with the IGB_UIO driver in our DPDK application.
Is there any documentation where we need to start to run a DPDK application
with minimal system capability?
Also please let us know if there is any known dependency with DPDK versions
(dpdk application with 18, 19.11 versions etc) when we run with sys capabilit.
Hi David,
Can you please share with us the pointer for OVS integration(DPDK running
as non-privileged mode ?)
Thanks,
Kamaraj
On Mon, Aug 30, 2021 at 5:36 PM David Marchand <david.marchand@redhat.com>
wrote:
> On Mon, Aug 30, 2021 at 1:59 PM Thomas Monjalon <thomas@monjalon.net>
> wrote:
> >
> > 30/08/2021 13:26, Ferruh Yigit:
> > > 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.
> >
> > I started working on such documentation, focusing on mlx5 use case.
> > I need more time to complete it.
> >
> > > If we are agree, perhaps we can find a volunteer in the tech board for
> it.
> >
> > I would be volunteer, and welcome any help.
>
> OVS already did some integration for this, and I can help too.
>
>
> --
> David Marchand
>
>
next prev parent reply other threads:[~2021-08-31 15: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
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 [this message]
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='CAG8PAaqaGCh_2uJhK=DV9eU66wnyd-VkpL3r8uocOzcXRx+mwQ@mail.gmail.com' \
--to=pkamaraj@gmail.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hpai@cisco.com \
--cc=kalas@cisco.com \
--cc=ksimha@cisco.com \
--cc=ppitchai@cisco.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).