Hi David,
It was a misunderstanding on my part. I had assumed that since the
libraries were not dynamically linked and not showing up in ldd output,
testpmd was probably not using netvsc.
After looking at the comments in config/meson.build " NOTE: DPDK always
builds both shared and static libraries.  Please set "default_library" to
either "static" or "shared" to select default linkage
 for apps and any examples.''')", I inferred that the libraries were being
linked statically.

Following this, i changed the default options in meson.build
default_library=shared from static and added deps in testpmd/meson.build
file as below:

+if dpdk_conf.has('RTE_NET_NETVSC')
+    deps += 'net_netvsc'
+endif
Now ldd dpdk-testpmd  shows netvsc pmd being linked dynamically and also
functional at run time.
Regards,
Nandini

On Mon, Jun 10, 2024 at 12:51 AM David Marchand <david.marchand@redhat.com>
wrote:

> 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
>
>

-- 
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.