| Message ID | 20240228121000.526645-1-bigeasy@linutronix.de (mailing list archive) |
|---|---|
| Headers | show |
| Series | net: Provide SMP threads for backlog NAPI | expand |
On Wed, 28 Feb 2024 13:05:47 +0100 Sebastian Andrzej Siewior wrote: > The RPS code and "deferred skb free" both send IPI/ function call > to a remote CPU in which a softirq is raised. This leads to a warning on > PREEMPT_RT because raising softiqrs from function call led to undesired > behaviour in the past. I had duct tape in RT for the "deferred skb free" > and Wander Lairson Costa reported the RPS case. > > This series only provides support for SMP threads for backlog NAPI, I > did not attach a patch to make it default and remove the IPI related > code to avoid confusion. I can post it for reference it asked. > > The RedHat performance team was so kind to provide some testing here. > The series (with the IPI code removed) has been tested and no regression > vs without the series has been found. For testing iperf3 was used on 25G > interface, provided by mlx5, ix40e or ice driver and RPS was enabled. I > can provide the individual test results if needed. Acked-by: Jakub Kicinski <kuba@kernel.org>
The RPS code and "deferred skb free" both send IPI/ function call to a remote CPU in which a softirq is raised. This leads to a warning on PREEMPT_RT because raising softiqrs from function call led to undesired behaviour in the past. I had duct tape in RT for the "deferred skb free" and Wander Lairson Costa reported the RPS case. This series only provides support for SMP threads for backlog NAPI, I did not attach a patch to make it default and remove the IPI related code to avoid confusion. I can post it for reference it asked. The RedHat performance team was so kind to provide some testing here. The series (with the IPI code removed) has been tested and no regression vs without the series has been found. For testing iperf3 was used on 25G interface, provided by mlx5, ix40e or ice driver and RPS was enabled. I can provide the individual test results if needed. Changes: - v2…v3 https://lore.kernel.org/all/20240221172032.78737-1-bigeasy@linutronix.de/ - Move the "if use_backlog_threads()" case into the CONFIG_RPS block within napi_schedule_rps(). - Use __napi_schedule_irqoff() instead of napi_schedule_rps() in kick_defer_list_purge(). - v1…v2 https://lore.kernel.org/all/20230929162121.1822900-1-bigeasy@linutronix.de/ - Patch #1 is new. It ensures that NAPI_STATE_SCHED_THREADED is always set (instead conditional based on task state) and the smboot thread logic relies on this bit now. In v1 NAPI_STATE_SCHED was used but is racy. - The defer list clean up is split out and also relies on NAPI_STATE_SCHED_THREADED. This fixes a different race. - RFC…v1 https://lore.kernel.org/all/20230814093528.117342-1-bigeasy@linutronix.de/ - Patch #2 has been removed. Removing the warning is still an option. - There are two patches in the series: - Patch #1 always creates backlog threads - Patch #2 creates the backlog threads if requested at boot time, mandatory on PREEMPT_RT. So it is either or and I wanted to show how both look like. - The kernel test robot reported a performance regression with loopback (stress-ng --udp X --udp-ops Y) against the RFC version. The regression is now avoided by using local-NAPI if backlog processing is requested on the local CPU. Sebastian