Hi Stephen, 

Attached is the configuration params copied in the text file. 
Please let me know your pointers on the same. 

Thanks,
Raghava Dattu.

-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org> 
Sent: Monday, October 10, 2022 8:27 PM
To: Dattu Gundu <dattu.gundu@oracle.com>
Cc: users@dpdk.org
Subject: Re: [External] : Re: qdisc errors on Azure VM (TAP Config)

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://urldefense.com/v3/__https://learn.microsoft.com/en-us/azure/vi
> rtual-network/setup-dpdk*failsafe-pmd__;Iw!!ACWV5N9M2RV99hQ!J1klGbmI3G
> hjDMaK_nhIjk-kotds2kG4eitQaqILXoazlhaeYkh8tmoAbZ-eH6kJet2dO3-EGJtPxMx2
> 1PM3bT6k$ 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.