DPDK usage discussions
 help / color / mirror / Atom feed
From: Cliff Burdick <shaklee3@gmail.com>
To: animesh tripathi <anitrip.444@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: running dpdk on mellanox with dpdk 21.08
Date: Thu, 7 Jul 2022 07:46:53 -0700	[thread overview]
Message-ID: <CA+Gp1nYveVgbym-MKzKoSwWff5D8T7yzQy85e+LNnmVkJ4UEbQ@mail.gmail.com> (raw)
In-Reply-To: <CAMH6JP9yWncGu8tX6q8ForoXQ69wUqd6ga4F6Nw6pxA+KD9fkQ@mail.gmail.com>

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

Please paste the output of the meson command. Are you running as root?


On Thu, Jul 7, 2022, 06:13 animesh tripathi <anitrip.444@gmail.com> wrote:

> Hi Team,
>
> I have to run dpdk on mellanox nic. I have compiled dpdk 21.08 with the
> following commands:
>
> meson --prefix=$(pwd)/build build
> ninja -C build
> ninja -C build install
> ldconfig
>
> While running the application I am getting following error:
>
> EAL: Detected 24 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Auto-detected process type: PRIMARY
> EAL: Detected static linkage of DPDK
> EAL: failed to parse device "0000:b5:00.1"
> EAL: Unable to parse device '0000:b5:00.1'
> PANIC in nr_dpdk_init():
> Cannot init EAL: No such device
> 6: [./a() [0x444179]]
> 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)
> [0x7f08e0f2e0b3]]
> 4: [./a(main+0x428) [0x4431f8]]
> 3: [./a(nr_dpdk_init+0x268) [0x509bd8]]
> 2: [./a(__rte_panic+0xcd) [0x43c55e]]
> 1: [./a(rte_dump_stack+0x32) [0x539ed2]]
>
> Also I cannot find mlx5 compiled libs in the dpdk build folder. Please
> help me in resolving this issue.
>
> Thanks,
> Animesh Tripathi
>

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

  reply	other threads:[~2022-07-07 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 13:12 animesh tripathi
2022-07-07 14:46 ` Cliff Burdick [this message]
2022-07-08  4:59   ` animesh tripathi
2022-07-08  6:12     ` animesh tripathi
2022-07-08 10:33       ` animesh tripathi
2022-07-12  6:35         ` animesh tripathi
2022-07-15 22:20           ` Cliff Burdick

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=CA+Gp1nYveVgbym-MKzKoSwWff5D8T7yzQy85e+LNnmVkJ4UEbQ@mail.gmail.com \
    --to=shaklee3@gmail.com \
    --cc=anitrip.444@gmail.com \
    --cc=users@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).