DPDK usage discussions
 help / color / mirror / Atom feed
From: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Marchand <david.marchand@redhat.com>, users@dpdk.org
Subject: Re: Compiling testpmd with DPDK netvsc PMD
Date: Tue, 11 Jun 2024 10:00:22 -0700	[thread overview]
Message-ID: <CAAkQrK8u=FmA3E9Dof5rWjwtnOi7Yn9vDQ4xwuSvYPE6Jq=bFQ@mail.gmail.com> (raw)
In-Reply-To: <20240611073540.783cbd81@hermes.local>

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

Hi Stephen,
It does include the driver and has been bounded as described in the
documentation.
Regards,
Nandini

On Tue, Jun 11, 2024 at 7:35 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> On Mon, 10 Jun 2024 09:50:42 +0200
> 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.
> >
> >
>
> Does the openwrt kernel include the uio_hv_generic driver?
> Did you bind the network device to uio_hv_generic as described in the
> documentation: https://doc.dpdk.org/guides/nics/netvsc.html
>
>

-- 
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: 3709 bytes --]

  reply	other threads:[~2024-06-11 17:00 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
2024-06-11 14:35       ` Stephen Hemminger
2024-06-11 17:00         ` Nandini Rangaswamy [this message]
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='CAAkQrK8u=FmA3E9Dof5rWjwtnOi7Yn9vDQ4xwuSvYPE6Jq=bFQ@mail.gmail.com' \
    --to=nandini.rangaswamy@broadcom.com \
    --cc=david.marchand@redhat.com \
    --cc=stephen@networkplumber.org \
    --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).