DPDK usage discussions
 help / color / mirror / Atom feed
From: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
To: users@dpdk.org
Subject: Compiling testpmd with DPDK netvsc PMD
Date: Thu, 6 Jun 2024 14:31:53 -0700	[thread overview]
Message-ID: <CAAkQrK_=vGDaNVR9dweNSpHxpAZOqW4T=WHU64WS2Wbw4-J_LQ@mail.gmail.com> (raw)

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

Hello,
I tried compiling the testpmd with DPDK netvsc for openwrt by setting
CONFIG_RTE_LIBRTE_NETVSC_PMD=y .

However, when I check ldd testpmd, it does not show any of the dpdk shared
libraries including net_netvsc linked to testpmd binary.
ldd dpdk-testpmd
        linux-vdso.so.1 (0x00007ffca1467000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ffb08134000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ffb0812f000)
        libelf.so.1 => /usr/lib/x86_64-linux-gnu/libelf.so.1
(0x00007ffb08111000)
        libpcap.so.1 => not found
        libmlx5.so.1 => /usr/lib/x86_64-linux-gnu/libmlx5.so.1
(0x00007ffb08093000)
        libibverbs.so.1 => /usr/lib/x86_64-linux-gnu/libibverbs.so.1
(0x00007ffb0806d000)
        libIPSec_MB.so.1 => not found
        libcrypto.so.3 => /usr/lib/x86_64-linux-gnu/libcrypto.so.3
(0x00007ffb07c29000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007ffb07c09000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007ffb07c04000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ffb079db000)
        /lib64/ld-linux-x86-64.so.2 (0x00007ffb097c1000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007ffb079bd000)
        libnl-route-3.so.200 =>
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200 (0x00007ffb0793a000)
        libnl-3.so.200 => /lib/x86_64-linux-gnu/libnl-3.so.200
(0x00007ffb07917000)

Any ideas on what I am missing here.
Regards,
Nandini

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

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

             reply	other threads:[~2024-06-06 21:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 21:31 Nandini Rangaswamy [this message]
2024-06-07 10:56 ` David Marchand
2024-06-07 23:31   ` Nandini Rangaswamy
2024-06-10  7:50     ` David Marchand
2024-06-11 14:35       ` Stephen Hemminger
2024-06-11 17:00         ` Nandini Rangaswamy
2024-06-11 17:10       ` Nandini Rangaswamy
2024-06-12  6:20         ` David Marchand
2024-06-12 14:48     ` Stephen Hemminger
2024-06-12 18:53       ` Nandini Rangaswamy

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='CAAkQrK_=vGDaNVR9dweNSpHxpAZOqW4T=WHU64WS2Wbw4-J_LQ@mail.gmail.com' \
    --to=nandini.rangaswamy@broadcom.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).