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: Mon, 5 Jul 2021 09:24:01 -0700 [thread overview]
Message-ID: <20210705092401.6a007088@hermes.local> (raw)
In-Reply-To: <fc993f62-e0e9-4303-9dd8-ce60bb0bfc26@www.fastmail.com>
On Mon, 05 Jul 2021 07:05:14 -0400
"Tyler Blair" <tblair@fastmail.com> wrote:
> Hi Stephen,
>
> > Some of the Linux distros have packaged those intokernels extras type packages.
> > 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.
>
> I installed *linux-azure-lts-20.04* and *linux-modules-extra-azure-lts-20.04* to no avail - is this the extras package you are referring to? The extra one maps to *linux-modules-extra-5.4.0-1051-azure*.
>
> > Or just use netvsc PMD and avoid the problem.
>
> This is what we use ( --vdev=net_vdev_netvsc0,iface=eth1 ) so I expect the messages are harmless - just wanted to check if there was a way to hide the message.
>
> Regards,
> Tyler
What does the following give:
~ $ /sbin/modinfo cls_flower
filename: /lib/modules/5.10.0-7-amd64/kernel/net/sched/cls_flower.ko
license: GPL v2
description: Flower classifier
author: Jiri Pirko <jiri@resnulli.us>
~ $ /sbin/modinfo sch_ingress
filename: /lib/modules/5.10.0-7-amd64/kernel/net/sched/sch_ingress.ko
license: GPL
alias: sch_clsact
depends:
retpoline: Y
intree: Y
name: sch_ingress
vermagic: 5.10.0-7-amd64 SMP mod_unload modversions
Also check kernel log with dmesg.
next prev parent reply other threads:[~2021-07-05 16:24 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
2021-07-05 11:05 ` Tyler Blair
2021-07-05 16:24 ` Stephen Hemminger [this message]
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=20210705092401.6a007088@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).