Hello everybody,
We are working on LX2160ARDB Rev1 board. The last version that LSDK supports LX2160ARDB Rev1 is 20.04, so we are using LSDK 20.04.
We are trying to use Linux network stack and DPDK applications both at the same time, Like shows in this example "https://community.nxp.com/t5/QorIQ-Knowledge-Base/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-..."
When we follow the steps in example, the ldpdmux's link states are down. Therefore we can not ping to PC.
So, we decided to change described steps as compatible as our setup the appropriate way. We have only one connected port, it is board's DPMAC17.
Here is a two different approach we tried;
1. We created a DPDMUX. Uplink interface dpdmux.0.0 connected to DPMAC.17. Linux Kernel uses DPNI that connected to dpdmux.0.1. DPDK application uses DPNI that connected to dpdmux.0.2.
2. We created a DPSW. Uplink interface dpsw.0.0 connected to DPMAC.17. Linux Kernel uses DPNI that connected to dpsw.0.1. DPDK application uses DPNI that connected to dpsw.0.2.
After first approach;
DPDMUX interface's link states are up for DPNI3 (that using by kernel) and dpmac17 (that port connected).
DPNI2 (that using by DPDK) is down, because no DPDK app is running at this stage.
We gave ip addresses to eth2 but we couldnt ping to PC.
After second approach;
DPSW interface's link states are up for DPNI3 (that using by kernel) and dpmac17 (that port connected).
DPNI2 (that using by DPDK) is down, because no DPDK app is running at this stage.
We gave ip addresses to eth2 and we could ping to PC. But when we run a DPDK App(Even helloworld that not uses any Network Interface) we lost connection between Linux Kernel and PC.
Here are outputs for these approaches:
My First question is; why we are not able ping to PC with DPDMUX approach?
Second one is; Why dpsw's link states are going down when we runs a DPDK App(Even helloworld that not uses any Network Interface) with DPSW approach?
Thank you all,
Best Regards
Serhat
Please try with following
1. Upgrade MC firmware to 10.25 or later
2. Make sure you have following patches (assuming 4.19)