From: Björn Töpel <bjorn.topel@xxxxxxxxx> The NAPI budget (NAPI_POLL_WEIGHT), meaning the number of received packets that are allowed to be processed for each NAPI invocation, takes into consideration that each received packet is aimed for the kernel networking stack. That is not the case for the AF_XDP receive path, where the cost of each packet is significantly less. Therefore, this commit adds a new NAPI budget, which is the NAPI_POLL_WEIGHT scaled by 4. Typically that would be 256 in most configuration. It is encouraged that AF_XDP zero-copy capable drivers use the XSK_NAPI_WEIGHT, when zero-copy is enabled. Processing 256 packets targeted for AF_XDP is still less work than 64 (NAPI_POLL_WEIGHT) packets going to the kernel networking stack. Signed-off-by: Björn Töpel <bjorn.topel@xxxxxxxxx> --- include/net/xdp_sock_drv.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/include/net/xdp_sock_drv.h b/include/net/xdp_sock_drv.h index 5b1ee8a9976d..4fc8e931d56f 100644 --- a/include/net/xdp_sock_drv.h +++ b/include/net/xdp_sock_drv.h @@ -7,8 +7,11 @@ #define _LINUX_XDP_SOCK_DRV_H #include <net/xdp_sock.h> +#include <linux/netdevice.h> #include <net/xsk_buff_pool.h> +#define XSK_NAPI_WEIGHT (NAPI_POLL_WEIGHT << 2) + #ifdef CONFIG_XDP_SOCKETS void xsk_tx_completed(struct xsk_buff_pool *pool, u32 nb_entries); -- 2.25.1
