Layerscape中的主题 Re: Congestion Management using DPAA in LS1043ARDB

Congestion Management using DPAA in LS1043ARDB

matt321 — Thu, 14 Sep 2023 06:32:12 GMT

Hi,

I'm performing performance tests in LS1043ARDB. I generated a packet storm using iperf and I could observe CPU cores are getting loaded to its maximum.

Also, I verified utilizing single core for handling these packets.

Now, I'm verifying how to limit the CPU load to 50% using DPAA queue management.

I could find few user guides explaining this, but I wanted to know how to configure DPAA for 50% core utilization from userspace.

Thanks and Regards

#ls1043ardb, #yocto, @yipingwang

Re: Congestion Management using DPAA in LS1043ARDB

yipingwang — Thu, 21 Sep 2023 09:12:43 GMT

Please refer to the following update from the AE team.

It seems there is no known tool to adjust CPU utilization.
I will query to dpaa1 development team.
Would customer to use "cpulimit" to have a trail?

Re: Congestion Management using DPAA in LS1043ARDB

matt321 — Mon, 25 Sep 2023 11:57:50 GMT

Thanks for your response.

I have tried cpulimit. But still during storming, softirqd is taking more CPU usage for queuing IRQ.

Basically, I want to stop this queuing when CPU utilization is 50%.

I want to implement the concept in this image, could you help me in understanding how I can configure this?

Re: Congestion Management using DPAA in LS1043ARDB

yipingwang — Thu, 28 Sep 2023 07:05:08 GMT

Please refer to the following update from the AE team.

What is the real problem they are trying to solve? They say they generate a packet storm, it seems to be a theoretical performance test. Are they looking to achieve a certain throughput and the CPU is the bottleneck?

Have they tried using DPDK for better CPU loads? Or FMan PCDs to better distribute the traffic?

One QMan-specific feature they could try to adjust is the DQRR interrupt threshold/time-out period. In the SDK DPAA1 driver the values are set at build (CONFIG_FSL_QMAN_PIRQ_DQRR_ITHRESH, CONFIG_FSL_QMAN_PIRQ_IPERIOD). In the upstream DPAA1 driver, these values can be changed at run time with ethtool IRQ coalescing commands.

The best way to limit the DPAA's access to the CPUs is by changing the irq affinity to use only 2/4 cores.

I don't know any ways to limit an irq or a driver to use only 50% of a core. They could use nice/cpulimit for the userspace processes, but I am not aware of any equivalent for the kernel.