Re: [dpdk-users] Running a second DPDK process that prints the NIC's link status/speed causes the first DPDK process to stop transmitting.

Re: [dpdk-users] Running a second DPDK process that prints the NIC's link status/speed causes the first DPDK process to stop transmitting.

[Antoine POLLENUS]

Francis

You should read these 2 resources  on how DPDK multi process works:

https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html

https://doc.dpdk.org/guides/sample_app_ug/multi_process.html

and most specifically this one :

https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html#multi-process-limitations

The delivery of interrupts, such as Ethernet* device link status interrupts, do not work in secondary processes. All interrupts are triggered inside the primary process only. Any application needing interrupt notification in multiple processes should provide its own mechanism to transfer the interrupt information from the primary process to any secondary process that needs the information.


Regards

Antoine

[dpdk-users] Running a second DPDK process that prints the NIC's link status/speed causes the first DPDK process to stop transmitting.

[Francis Rammeloo]

I have a small utility application that lists the DPDK interfaces and
prints their link status and link speed. Running this utility while another
DPDK application is running causes that application to enter a seemingly
corrupt state (all transmissions start failing). Apparently the call to
rte_eal_init in the second app is sufficient to break the first app.

Is there a way to avoid this problem?


Francis