From: David Marchand <david.marchand@redhat.com>
To: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
Cc: users@dpdk.org
Subject: Re: Compiling testpmd with DPDK netvsc PMD
Date: Mon, 10 Jun 2024 09:50:42 +0200 [thread overview]
Message-ID: <CAJFAV8yxXinp=ARftH-PXinbfdzRtyaLgFersQCVBcVcjX_8kw@mail.gmail.com> (raw)
In-Reply-To: <CAAkQrK_Rv_1HPZsuOvh2Bj1mptxt-Nex4y=zQV_i2XkLumHhAQ@mail.gmail.com>
Hello,
On Sat, Jun 8, 2024 at 1:32 AM Nandini Rangaswamy
<nandini.rangaswamy@broadcom.com> wrote:
> Thanks for your email. I inspected meson build output and do see that netvsc is in the list of enabled drivers.
> ===============
> Drivers Enabled
> ===============
>
> common:
> iavf, mlx5, qat,
> bus:
> auxiliary, pci, vdev, vmbus,
> mempool:
> bucket, ring, stack,
> dma:
>
> net:
> af_packet, bond, e1000, ena, failsafe, gve, i40e, iavf,
> ice, igc, ixgbe, kni, mlx5, netvsc, ring, tap,
> vdev_netvsc, vhost, virtio, vmxnet3,
Ok, so the driver seems indeed part of this build, yet it was not
functional at runtime?
Could you confirm this driver was indeed embeeded in (*statically*
linked) testpmd?
$ ./usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd | grep -i vsc
"name": "net_netvsc",
"name": "net_vdev_netvsc",
>
> Also, i changed the meson.build default_library=shared from static and it worked.
Mm, the fact that changing link mode fixes the issue points at a link issue.
There is a bug with old pkg-config tool (<= 0.27 iirc) that does not
process correctly dpdk .pc (for static link).
It is worth checking which version of pkgconf is used in openwrt.
--
David Marchand
next prev parent reply other threads:[~2024-06-10 7:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 21:31 Nandini Rangaswamy
2024-06-07 10:56 ` David Marchand
2024-06-07 23:31 ` Nandini Rangaswamy
2024-06-10 7:50 ` David Marchand [this message]
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='CAJFAV8yxXinp=ARftH-PXinbfdzRtyaLgFersQCVBcVcjX_8kw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=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).