DPDK patches and discussions
 help / color / mirror / Atom feed
From: Acdam Bacdam <acdam.bacdam@gmail.com>
To: dev@dpdk.org
Subject: Running DPDK KNI sample App in K8 Pod
Date: Wed, 29 Jun 2022 19:03:53 +0530	[thread overview]
Message-ID: <CAEJRUnZt8==1uM9v4WVjbPor8jbwy1PG4XdbBr5K2Xy0e5o6jQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

Hi Experts,

I am trying to run a DPDK KNI based sample app inside the K8 Pod
environment, but I am not able to do so without host-network permissions.

I tried using KNI based sample application provided under DPDK 19.11
version, but it failed to create vEth0 inside the PoD environment *without
host-network* permissions, though ifconfig shows vEth0 but it's not present
under (/sys/devices/virtual/net/).

As sample app uses dpdk kni api rte_kni_update_link, which internally uses
this path(/sys/devices/virtual/net/vEth0/carrier) to bring vEth UP, but
this path is not present hence failure in bringing UP the state of vEth.

taskset 10 ./build/kni -c0x30 -n4 -- -P -p0x1 -m --config="(0,4,4)"

[root@server ~]# ls /sys/devices/virtual/net/vEth0
ls: cannot access /sys/devices/virtual/net/vEth0: No such file or directory
[root@server ~]#

As soon as the pod is deployed *with host-network* permissions, whole
network is available inside PoD with all required permissions and DPDK is
able to create vEth (which creates /sys/devices/virtual/net/vEth0/carrier
path) and sample app is able to update the link state of vEth and works
perfectly fine.

Any suggestions on what can be done to make it work inside a PoD
environment without host-network permissions ?

Best Regards,

[-- Attachment #2: Type: text/html, Size: 1613 bytes --]

                 reply	other threads:[~2022-06-29 14:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAEJRUnZt8==1uM9v4WVjbPor8jbwy1PG4XdbBr5K2Xy0e5o6jQ@mail.gmail.com' \
    --to=acdam.bacdam@gmail.com \
    --cc=dev@dpdk.org \
    /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).