Hi, You can create a simple setup with only running testpmd with primary and another testpmd with secondary and then see the results.
No, the reason for the primary process termination could be close or shutdown (ctrl + c or ctrl + q) or any other. The reason is clear: "In secondary processes, accessing 'dev->data->dev_private' or &dev->data->mac_addrs directly can cause a segmentation fault if the primary process has exited or the shared memory is unavailable." The effect is throughput the life-cycle of secondary process existence in dpdk after primary, You can check https://patches.dpdk.org/project/dpdk/patch/20250721073851.963141-1-14pwcse1...@uetpeshawar.edu.pk/ https://patches.dpdk.org/project/dpdk/patch/20250721105522.1019515-1-14pwcse1...@uetpeshawar.edu.pk/ I think most of the details have already been provided. The community agrees with the current solution. Thanks.
