MC version upgrade with DPDK application compatibility

jackho · ‎05-09-2024

Hi,

We are running DPDK version 19.11.6-rc1 with MC version 10.35, now we want to upgrade MC version to 10.36, some questions below want to confirm with you:

1. Does MC firmware version have a compatibility problem with DPDK version?

2. From the MC binary CHANGELOG.md file content, it seems MC 10.36 fix some dpaa2 issue.

Is it will affect DPDK initial flow? If yes, is there anything we should know to modify DPDK initial flow to fit MC version upgrade?

Thank you.

BR,

Jack Ho

yipingwang · ‎05-15-2024

One more thing

Customer has not clarified if they are using the latest commits from NXP 19.11-qoriq branch

https://github.com/NXP/dpdk/

branch: 19.11-qroiq

They will need minimum tag: LSDK20.04-isc-16

MC 10.36 compatibility was fixed at: https://github.com/NXP/dpdk/commit/ad8138fa3e85e557d4b6e29e72851b23f1a9cfd5

The latest tag is : LSDK20.04-isc-19

View solution in original post

yipingwang · ‎05-12-2024

Confirming with NXP DPDK team.

yipingwang · ‎05-13-2024

I got confirmation from NXP DPDK development team.

MC binaries are typically backward compatible. So it will work without any issue with DPDK 19.11.6

I will also suggest, it will be better to migrate to MC 10.38.1

jackho · ‎05-14-2024

Hi @yipingwang,

Actually, we face an issue when upgrade MC version from 10.35 to 10.36, dpdk version is based on 19.11-rc6, we are using following method to create dpdk:

echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind
restool dpni destroy dpni.2
export DPDMAI_COUNT=0
export DPIO_COUNT=16
/usr/local/dpdk/dpaa2/dynamic_dpl.sh dpni dpni -b 00:00:00:00:21:00
/usr/local/dpdk/dpaa2/dynamic_dpl.sh dpni.3 dpni -b 00:00:00:00:22:00
ls-addni --no-link --mac-addr=<mac address>
sleep 2
echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/unbind

#DPD MUX is created as below with CUSTOM METHOD
restool dpdmux create --default-if=1 --num-ifs=2 --method DPDMUX_METHOD_CUSTOM --manip=DPDMUX_MANIP_NONE --option=DPDMUX_OPT_CLS_MASK_SUPPORT --container=dprc.1
restool dprc connect dprc.1 --endpoint1=dpdmux.0.0 --endpoint2=dpmac.3
restool dprc connect dprc.1 --endpoint1=dpdmux.0.1 --endpoint2=dpni.6
restool dprc connect dprc.1 --endpoint1=dpdmux.0.2 --endpoint2=dpni.2
restool dprc assign dprc.1 --object=dpdmux.0 --child=dprc.2 --plugged=1
echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind

After dpdk init done, we start running our dpdk application,

it appears below error:

dpaa2_net: dpdmux_if_set_errors_behavior dpaa2_create_dpdmux_device err -22

dpaa2_net: Invalid dpdmux_id: 0

But in MC version 10.35 don't have these kinds of issue. we even try to upgrade MC version to 10.38, but issue still exist.

Could you help check with DPDK team what will cause this issue?

Is it related to DPDK version?

Thanks

BR.