From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6CFB5424CF for ; Tue, 11 Jun 2024 19:00:37 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DF45140698; Tue, 11 Jun 2024 19:00:36 +0200 (CEST) Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) by mails.dpdk.org (Postfix) with ESMTP id 04E834021F for ; Tue, 11 Jun 2024 19:00:34 +0200 (CEST) Received: by mail-lj1-f170.google.com with SMTP id 38308e7fff4ca-2ebe40673d8so12430051fa.3 for ; Tue, 11 Jun 2024 10:00:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1718125234; x=1718730034; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=s62PRFt3eCT6xcFgS8VPOZw3IiE1nUfZyokvOIcwhls=; b=VuF2S3YK9NpKDoxqvK8a/VhNttnrvpUMs+MNRvQCcYXNJaK1q1XWXJX9ccwz0iX9LI ETpa3FyFKuOQYI70EfMxtuwMrtElpAo6k2ixAQN0/1NqEmNqIR+gfe+XfwWOr1sl2zaS u7ex0Wyx0A0NNlQ+/YDSy1uizV2JdCSGuCZu4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718125234; x=1718730034; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=s62PRFt3eCT6xcFgS8VPOZw3IiE1nUfZyokvOIcwhls=; b=XaMD9pqOiWKjohnDb514xo5bXxw3ObO+b/Q+WJ2DEPEW7YtdLkAWwpVnLE5Ffu2jQU XhRI32+Vy8mRS7lnXVcMV6IfZ/WMDB67tJ8lUss4+ebmQLhXIxS/9mi3G35gQREUCGHA UP3EnPmIvUJYOONo2EyN2K0T92LR4a076SokH3bl/eDQMBn+O+bY2IUuWovdcFj0WZDk VMNgxFs3dWdri7xw5S4xXOpUhdKTHumpAUyIad/8+FaabD95aRPWbvO7mIOJZTfxrqxG 2RaPjM92S0WEECsQnBAou6UPmEjfJAGAHh2xflaEZv5f3xasf9cs+11UJmMeQwkjL3DP QmVg== X-Forwarded-Encrypted: i=1; AJvYcCUNc1aA1wUyAtscOokF5CeCrkHrEsdYGoSBwPr9o65JIBGGaBEUaGsTaZf0+4SeILfQG3AfW2jSjJmLUGru9Q== X-Gm-Message-State: AOJu0YxYH2tHX9SYPxLx0+mY2xrAhPwcxlwNqAr7SP0EdbyY5FBg4OGL 7Og7ahzyUAnbKfguUOxax3kkvAUWpV6uGg7AynsYjEgg4auY1MMsUB9pqrYSxM0+tGSv2HDDHJ1 6lFiOAa0iKJMYryaq5iwSyybKQmNvSKGE1lrbxn1borwBhak89gaqwtDTamOh2dwLb9+9Iotoab vSoQBC2s0= X-Google-Smtp-Source: AGHT+IHEhBAcpVXEy0GbUjDi4GuqhAxROn6Io8ly9jlXfHZ2yu0eSqKYQiaYkEmKQWbPov/BuGUz6egd+i2UQJh+n+Q= X-Received: by 2002:a2e:9216:0:b0:2eb:d92c:58f8 with SMTP id 38308e7fff4ca-2ebd92c5b1emr50582191fa.19.1718125234191; Tue, 11 Jun 2024 10:00:34 -0700 (PDT) MIME-Version: 1.0 References: <20240611073540.783cbd81@hermes.local> In-Reply-To: <20240611073540.783cbd81@hermes.local> From: Nandini Rangaswamy Date: Tue, 11 Jun 2024 10:00:22 -0700 Message-ID: Subject: Re: Compiling testpmd with DPDK netvsc PMD To: Stephen Hemminger Cc: David Marchand , users@dpdk.org Content-Type: multipart/alternative; boundary="00000000000043a2a4061aa034f7" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --00000000000043a2a4061aa034f7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFAM Stephen Hemminger < stephen@networkplumber.org> wrote: > On Mon, 10 Jun 2024 09:50:42 +0200 > David Marchand wrote: > > > Hello, > > > > On Sat, Jun 8, 2024 at 1:32=E2=80=AFAM Nandini Rangaswamy > > wrote: > > > Thanks for your email. I inspected meson build output and do see that > netvsc is in the list of enabled drivers. > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > Drivers Enabled > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > 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=3Dshared 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 (<=3D 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 > > --=20 This electronic communication and the information and any files transmitted= =20 with it, or attached to it, are confidential and are intended solely for=20 the use of the individual or entity to whom it is addressed and may contain= =20 information that is confidential, legally privileged, protected by privacy= =20 laws, or otherwise restricted from disclosure to anyone else. If you are=20 not the intended recipient or the person responsible for delivering the=20 e-mail to the intended recipient, you are hereby notified that any use,=20 copying, distributing, dissemination, forwarding, printing, or copying of= =20 this e-mail is strictly prohibited. If you received this e-mail in error,= =20 please return the e-mail to the sender, delete it from your computer, and= =20 destroy any printed copy of it. --00000000000043a2a4061aa034f7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Stephen,
It does include=C2=A0the driver and has be= en bounded as described in the documentation.
Regards,
= Nandini

On Tue, Jun 11, 2024 at 7:35=E2=80=AFAM 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=E2=80=AFAM 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.
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > Drivers Enabled
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > common:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0iavf, mlx5, qat,
> > bus:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0auxiliary, pci, vdev, vmbus,
> > mempool:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bucket, ring, stack,
> > dma:
> >
> > net:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0af_packet, bond, e1000, ena, fai= lsafe, gve, i40e, iavf,
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ice, igc, ixgbe, kni, mlx5, netv= sc, ring, tap,
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0vdev_netvsc, vhost, virtio, vmxn= et3,=C2=A0
>
> 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
>=C2=A0 =C2=A0 =C2=A0"name": "net_netvsc",
>=C2=A0 =C2=A0 =C2=A0"name": "net_vdev_netvsc",
>
>
> >
> > Also, i changed the meson.build default_library=3Dshared from sta= tic and it worked.=C2=A0
>
> Mm, the fact that changing link mode fixes the issue points at a link = issue.
>
> There is a bug with old pkg-config tool (<=3D 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.h= tml


This ele= ctronic communication and the information and any files transmitted with it= , or attached to it, are confidential and are intended solely for the use o= f the individual or entity to whom it is addressed and may contain informat= ion that is confidential, legally privileged, protected by privacy laws, or= otherwise restricted from disclosure to anyone else. If you are not the in= tended recipient or the person responsible for delivering the e-mail to the= intended recipient, you are hereby notified that any use, copying, distrib= uting, dissemination, forwarding, printing, or copying of this e-mail is st= rictly 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. --00000000000043a2a4061aa034f7--