From: Stephen Hemminger <stephen@networkplumber.org>
To: "Tyler Blair" <tblair@fastmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] qdisc errors on 20.11.1 & Azure
Date: Tue, 29 Jun 2021 10:43:35 -0700 [thread overview]
Message-ID: <20210629104335.0fb73114@hermes.local> (raw)
In-Reply-To: <91abe2f9-82e0-45f0-9d7c-d9d5bf70d4f2@www.fastmail.com>
On Mon, 28 Jun 2021 07:36:12 -0400
"Tyler Blair" <tblair@fastmail.com> wrote:
> Hi,
>
> I'm seeing what looks like benign errors from qdisc on testpmd & our DPDK app on Azure. I'm wondering if anyone knows of a way to 'fix' these?
>
> EAL: Detected 8 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Detected static linkage of DPDK
> EAL: Selected IOVA mode 'VA'
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: Probe PCI driver: mlx5_pci (15b3:1016) device: 2a8d:00:02.0 (socket 0)
> EAL: Probe PCI driver: mlx5_pci (15b3:1016) device: 5ed7:00:02.0 (socket 0)
> net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3)*
> *
> *tap_nl_dump_ext_ack(): Cannot delete qdisc with handle of zero**
> *
> *tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid**
> *
> *tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid**
> *
> *tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid**
> *
> *tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid**
> *
> *tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid**
> *
> *tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid**
> *
> *tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid**
> *
> *tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid*
> [...]
>
> It's not causing any issues that I can see, I'm just wondering if there's a cause for this in the environment that we can fix so we don't have benign errors showing up.
>
> Reproduced by running testpmd with no arguments on Azure:
>
> - OS: Ubuntu 20.04 5.4.0-1048-azure
> - DPDK: 20.11.1 (LTS)
> - Networking: Azure Accelerated Networking (netvsc)
>
> OS setup is pretty minimal, nothing special other than DPDK is installed.
>
> I don't recall these errors happening while on bare metal - only on Azure.
>
> Thanks!
>
> Regards,
> Tyler
In order to support the tap flow emulation you need to hve the ingress qdisc
and the flower qdisc. Some of the Linux distros have packaged those into
kernels extras type packages.
Or just use netvsc PMD and avoid the problem.
next prev parent reply other threads:[~2021-06-29 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 11:36 Tyler Blair
2021-06-29 17:43 ` Stephen Hemminger [this message]
2021-07-05 11:05 ` Tyler Blair
2021-07-05 16:24 ` Stephen Hemminger
2021-07-06 14:35 ` Tyler Blair
2021-07-06 14:57 ` Stephen Hemminger
2021-07-06 16:10 ` Tyler Blair
2021-07-07 16:05 ` Long Li
2021-07-13 12:56 ` Tyler Blair
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=20210629104335.0fb73114@hermes.local \
--to=stephen@networkplumber.org \
--cc=tblair@fastmail.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).