DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Dennis Montgomery <dmontgomery@juniper.net>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] How do I enable netvsc with meson build?
Date: Fri, 4 Jun 2021 11:30:09 -0700	[thread overview]
Message-ID: <20210604113009.1cdc2fb0@hermes.local> (raw)
In-Reply-To: <BLAPR05MB73005FD812035D855A833B4FA32C9@BLAPR05MB7300.namprd05.prod.outlook.com>

On Tue, 18 May 2021 10:28:04 +0000
Dennis Montgomery <dmontgomery@juniper.net> wrote:

> Hello DPDK community,
> 
> I’ve mislaid my copy of “Building DPDK with Meson for Dummies” and can’t figure this out: how do I enable the drivers/net/netvsc pmd with meson?  I’m finding that it’s disabled due to a missing dependency, but the dependency it claims to be missing… seems to be there?
> 
> Specifically it’s complaining about the vmbus driver.  That’s included in the meson.log snippet attached below, under “Drivers Enabled”/bus.  I’m lost.
> 
> Thanks for your help,
> 
> Dennis Montgomery
> 
> From meson.log:
> Message:
> =================
> Libraries Enabled
> =================
> 
> libs:
>      kvargs, telemetry, eal, ring, rcu, mempool, mbuf, net,
>      meter, ethdev, pci, cmdline, metrics, hash, timer, acl,
>      bbdev, bitratestats, cfgfile, compressdev, cryptodev, distributor, efd, eventdev,
>      gro, gso, ip_frag, jobstats, kni, latencystats, lpm, member,
>      power, pdump, rawdev, regexdev, reorder, sched, security, stack,
>      vhost, ipsec, port, table, pipeline, flow_classify, bpf,
> 
> Message:
> ===============
> Drivers Enabled
> ===============
> 
> common:
>      cpt, dpaax, iavf, octeontx, octeontx2, mlx5,
> bus:
>      dpaa, fslmc, ifpga, pci, vdev, vmbus,
> mempool:
>      bucket, dpaa, dpaa2, octeontx, octeontx2, ring, stack,
> net:
>      af_packet, ark, atlantic, avp, axgbe, bond, bnx2x, bnxt,
>      cxgbe, dpaa, dpaa2, e1000, ena, enetc, enic, failsafe,
>      fm10k, i40e, hinic, hns3, iavf, ice, igc, ixgbe,
>      kni, liquidio, memif, mlx4, mlx5, nfp, null, octeontx,
>      octeontx2, pcap, qede, ring, sfc, softnic, tap, thunderx,
>      vdev_netvsc, vhost, virtio, vmxnet3,
> raw:
>      ioat, ntb, dpaa2_cmdif, dpaa2_qdma, octeontx2_dma, octeontx2_ep, skeleton,
> crypto:
>      caam_jr, dpaa_sec, dpaa2_sec, nitrox, null_crypto, octeontx_crypto, octeontx2_crypto, crypto_scheduler,
>      virtio_crypto,
> compress:
>      octeontx_compress, qat,
> regex:
>      mlx5,
> vdpa:
>      mlx5, ifc,
> event:
>      dpaa, dpaa2, octeontx2, opdl, skeleton, sw, dsw, octeontx,
> 
> baseband:
>      null, turbo_sw, fpga_lte_fec, fpga_5gnr_fec,
> 
> Message:
> =================
> Content Skipped
> =================
> 
> libs:
> 
> drivers:
>      common/mvep:    missing dependency, "libmusdk"
>      net/ipn3ke:     missing dependency, "libfdt"
>      net/netvsc:     missing dependency, DPDK VMBus driver
>      raw/ifpga: missing dependency, "libfdt"

Did this get resolved? I don't see this with 20.11.
Do you have the correct version of meson?


  reply	other threads:[~2021-06-04 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 10:28 Dennis Montgomery
2021-06-04 18:30 ` Stephen Hemminger [this message]
2021-06-04 19:22   ` Dennis Montgomery

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=20210604113009.1cdc2fb0@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dmontgomery@juniper.net \
    --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).