Re: [PATCH bpf-next 00/10] xsk: stop softirq processing on full XSK Rx queue

Maxim Mikityanskiy
2022-04-07T10:49:21Z

On 2022-04-05 14:06, Maciej Fijalkowski wrote:
> Hi!
>
> This is a revival of Bjorn's idea [0] to break NAPI loop when XSK Rx
> queue gets full which in turn makes it impossible to keep on
> successfully producing descriptors to XSK Rx ring. By breaking out of
> the driver side immediately we will give the user space opportunity for
> consuming descriptors from XSK Rx ring and therefore provide room in the
> ring so that HW Rx -> XSK Rx redirection can be done.
>
> Maxim asked and Jesper agreed on simplifying Bjorn's original API used
> for detecting the event of interest, so let's just simply check for
> -ENOBUFS within Intel's ZC drivers after an attempt to redirect a buffer
> to XSK Rx. No real need for redirect API extension.

I believe some of the other comments under the old series [0] might be
still relevant:

1. need_wakeup behavior. If need_wakeup is disabled, the expected
behavior is busy-looping in NAPI, you shouldn't break out early, as the
application does not restart NAPI, and the driver restarts it itself,
leading to a less efficient loop. If need_wakeup is enabled, it should
be set on ENOBUFS - I believe this is the case here, right?

2. 50/50 AF_XDP and XDP_TX mix usecase. By breaking out early, you
prevent further packets from being XDP_TXed, leading to unnecessary
latency increase. The new feature should be opt-in, otherwise such
usecases suffer.

3. When the driver receives ENOBUFS, it has to drop the packet before
returning to the application. It would be better experience if your
feature saved all N packets from being dropped, not just N-1.

4. A slow or malicious AF_XDP application may easily cause an overflow
of the hardware receive ring. Your feature introduces a mechanism to
pause the driver while the congestion is on the application side, but no
symmetric mechanism to pause the application when the driver is close to
an overflow. I don't know the behavior of Intel NICs on overflow, but in
our NICs it's considered a critical error, that is followed by a
recovery procedure, so it's not something that should happen under
normal workloads.

> One might ask why it is still relevant even after having proper busy
> poll support in place - here is the justification.
>
> For xdpsock that was:
> - run for l2fwd scenario,
> - app/driver processing took place on the same core in busy poll
> with 2048 budget,
> - HW ring sizes Tx 256, Rx 2048,
>
> this work improved throughput by 78% and reduced Rx queue full statistic
> bump by 99%.
>
> For testing ice, make sure that you have [1] present on your side.
>
> This set, besides the work described above, also carries also
> improvements around return codes in various XSK paths and lastly a minor
> optimization for xskq_cons_has_entries(), a helper that might be used
> when XSK Rx batching would make it to the kernel.

Regarding error codes, I would like them to be consistent across all
drivers, otherwise all the debuggability improvements are not useful
enough. Your series only changed Intel drivers. Here also applies the
backward compatibility concern: the same error codes than were in use
have been repurposed, which may confuse some of existing applications.

> Thanks!
> MF
>
> [0]: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fbpf%2F20200904135332.60259-1-bjorn.topel%40gmail.com%2F&amp;data=04%7C01%7Cmaximmi%40nvidia.com%7Cc9cefaa3a1cd465ccdb908da16f45eaf%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637847536077594100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=sLpTcgboo9YU55wtUtaY1%2F%2FbeiYxeWP5ubk%2FQ6X8vB8%3D&amp;reserved=0
> [1]: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fnetdev%2F20220317175727.340251-1-maciej.fijalkowski%40intel.com%2F&amp;data=04%7C01%7Cmaximmi%40nvidia.com%7Cc9cefaa3a1cd465ccdb908da16f45eaf%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637847536077594100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=OWXeZhc2Nouz%2FTMWBxvtTYbw%2FS8HWQfbfEqnVc5478k%3D&amp;reserved=0
>
> Björn Töpel (1):
> xsk: improve xdp_do_redirect() error codes
>
> Maciej Fijalkowski (9):
> xsk: diversify return codes in xsk_rcv_check()
> ice: xsk: terminate NAPI when XSK Rx queue gets full
> i40e: xsk: terminate NAPI when XSK Rx queue gets full
> ixgbe: xsk: terminate NAPI when XSK Rx queue gets full
> ice: xsk: diversify return values from xsk_wakeup call paths
> i40e: xsk: diversify return values from xsk_wakeup call paths
> ixgbe: xsk: diversify return values from xsk_wakeup call paths
> ice: xsk: avoid refilling single Rx descriptors
> xsk: drop ternary operator from xskq_cons_has_entries
>
> .../ethernet/intel/i40e/i40e_txrx_common.h | 1 +
> drivers/net/ethernet/intel/i40e/i40e_xsk.c | 27 +++++++++------
> drivers/net/ethernet/intel/ice/ice_txrx.h | 1 +
> drivers/net/ethernet/intel/ice/ice_xsk.c | 34 ++++++++++++-------
> .../ethernet/intel/ixgbe/ixgbe_txrx_common.h | 1 +
> drivers/net/ethernet/intel/ixgbe/ixgbe_xsk.c | 29 ++++++++++------
> net/xdp/xsk.c | 4 +--
> net/xdp/xsk_queue.h | 4 +--
> 8 files changed, 64 insertions(+), 37 deletions(-)
>