From: Stephen Hemminger <stephen@networkplumber.org>
To: Dattu Gundu <dattu.gundu@oracle.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [External] : Re: qdisc errors on Azure VM (TAP Config)
Date: Mon, 10 Oct 2022 07:56:32 -0700 [thread overview]
Message-ID: <20221010075632.7232d30c@hermes.local> (raw)
In-Reply-To: <SA1PR10MB6517020469B94E8D2519DD3890209@SA1PR10MB6517.namprd10.prod.outlook.com>
On Mon, 10 Oct 2022 08:05:26 +0000
Dattu Gundu <dattu.gundu@oracle.com> wrote:
> Hi Stephen,
>
> As Microsoft recommended in the below link to use the failsafe PMD in the AZURE.
> https://learn.microsoft.com/en-us/azure/virtual-network/setup-dpdk#failsafe-pmd
> So, we are using the failsafe/tap/vdev_netvsc in AZURE cloud VM's.
>
>
> Question1: Can we use failsafe on top of NETVSC PMD on AZURE ?
No. There is no reason to use failsave if you you use tne native netvsc PMD.
Netvsc PMD has internal support for the accelerated SRIOV path.
> Question2: Is there any alternatives on Azure cloud ?
There are two alternatives vdev_netvsc/failsafe/tap or netvsc PMD
> Question3: If no alternatives, what are the required packages to be installed for QDISC ?
>
>
>
> FYI,
>
> Flower, Mirred, Ingress already set in our config.
>
> /tmp # cat config | grep FLOW
> # CONFIG_NF_FLOW_TABLE is not set
> CONFIG_NET_CLS_FLOW=y
> CONFIG_NET_CLS_FLOWER=y
> CONFIG_NET_FLOW_LIMIT=y
> CONFIG_BNXT_FLOWER_OFFLOAD=y
>
> /tmp # cat config | grep INGRESS
> CONFIG_NET_INGRESS=y
> CONFIG_NETFILTER_INGRESS=y
> CONFIG_NET_SCH_INGRESS=y
>
> /tmp # cat config | grep MIRRED
> CONFIG_NET_ACT_MIRRED=y
>
> /tmp # cat config | grep MQPRIO
> # CONFIG_NET_SCH_MQPRIO is not set
> /tmp #
>
> Thanks,
> Raghava Dattu.
Plead post full kernel config for your custom kernel,
You will need the multi-queue prio qdisc to get the interface to TAP working.
next prev parent reply other threads:[~2022-10-10 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 6:08 Dattu Gundu
2022-10-06 16:31 ` Stephen Hemminger
2022-10-10 8:05 ` [External] : " Dattu Gundu
2022-10-10 14:56 ` Stephen Hemminger [this message]
2022-10-12 11:14 ` Dattu Gundu
2022-10-12 17:11 ` Stephen Hemminger
2022-10-17 9:13 ` Dattu Gundu
2022-10-17 15:01 ` Stephen Hemminger
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=20221010075632.7232d30c@hermes.local \
--to=stephen@networkplumber.org \
--cc=dattu.gundu@oracle.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).