DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Avijit  Pandey" <Avijit@voereir.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Error in rte_eal_init() when multiple PODs over single node of K8 cluster
Date: Wed, 27 Mar 2024 12:42:55 +0000	[thread overview]
Message-ID: <AS8PR02MB68374A2E9CBB30E6FA700300CC342@AS8PR02MB6837.eurprd02.prod.outlook.com> (raw)

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

Hello Devs,

I hope this email finds you well.
I am reaching out to seek assistance regarding an issue I am facing in DPDK within my Kubernetes cluster.

I have deployed a Kubernetes cluster v1.26.0, and I am currently running network testing through DPPD-PRoX (commit/02425932<https://github.com/opnfv/samplevnf/commit/02425932>) using DPDK (v22.11.0). I have deployed 3 pairs of PODs (3 server pods and 3 client pods) on a single K8 node. The server generates and sends traffic to the receiver pod.

During the automated testing, I encounter an error: "Error in rte_eal_init()." This error occurs randomly, and I am unable to determine the root cause. However, this issue does not occur when I use a single pair of PODs (1 server pod and 1 client pod). The traffic is sent and received through the sriov NICs.

PFB the software catalogue I am using:
DPPD-PRoX: commit/02425932<https://github.com/opnfv/samplevnf/commit/02425932>
DPDK version: v22.11.0
DPDK driver: vfio-pci
SRIOV VF driver: iavf
POD OS: Ubuntu 20.04
POD Kernel: 4.18.0-372.9.1.el8.x86_64
Kubernetes: v1.26.0

Error logs:

EAL: Detected CPU lcores: 104
EAL: Detected NUMA nodes: 2
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
EAL: Cannot allocate memzone list
EAL: FATAL: Cannot init memzone
EAL: Cannot init memzone
Supports Intel RDT Monitoring capability
        RDT-A. Supports Intel RDT Allocation capability
        Supports L3 Cache Intel RDT Monitoring
        Intel RDT Monitoring has 207 maximum RMID
        Supports L3 occupancy monitoring
        Supports L3 Total bandwidth monitoring
        Supports L3 Local bandwidth monitoring
        L3 Cache Intel RDT Monitoring Capability has 207 maximum RMID
        Upscaling_factor = 106496
        Supports L3 Cache Allocation Technology
        Supports MBA Allocation Technology
        Code and Data Prioritization Technology supported
        L3 Cache Allocation Technology Enumeration Highest COS number = 15
        L2 Cache Allocation Technology Enumeration COS number = 0
        Memory Bandwidth Allocation Enumeration COS number = 7
=== Parsing configuration file '/tmp/tmpwkvn651h.cfg' ===
        *** Reading [lua] section ***
        *** Reading [variables] section ***
        *** Reading [eal options] section ***
        *** Reading [cache set #] sections ***
        *** Reading [port #] sections ***
        *** Reading [defaults] section ***
        *** Reading [global] section ***
        *** Reading [core #] sections ***
=== Setting up RTE EAL ===
        Worker threads core mask is 0x2800000
        With master core index 23, full core mask is 0x2800000
        EAL command line: /opt/samplevnf/VNFs/DPPD-PROX/build/prox -c0x2800000 --main-lcore=23 -n4 --allow 0000:86:04.6
error   Error in rte_eal_init()


Any insights or guidance to help resolve this issue would be highly appreciated. If you need any more details, please feel free to ask.
Thank you for your time and assistance!



Best Regards,

Avijit Pandey
Cloud SME | VoerEirAB
+919598570190


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

             reply	other threads:[~2024-03-27 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 12:42 Avijit  Pandey [this message]
2024-03-27 14:55 ` Bruce Richardson
2024-04-01  7:38   ` Avijit  Pandey
2024-04-02  9:13     ` Bruce Richardson
2024-04-08  5:29       ` Avijit  Pandey

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=AS8PR02MB68374A2E9CBB30E6FA700300CC342@AS8PR02MB6837.eurprd02.prod.outlook.com \
    --to=avijit@voereir.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).