summaryrefslogtreecommitdiff
path: root/mm
diff options
context:
space:
mode:
authorJoshua Washington <joshwash@google.com>2024-12-20 19:28:06 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-01-09 13:33:54 +0100
commit86c9fd14aa7fdeeb2255eba9c4f99c075ed19b9a (patch)
tree764041aec5c2b10b5c9466bcb8218ed0aba50701 /mm
parent35f44eed5828cf1bc7e760d1993ed8549ba41c7b (diff)
downloadlinux-86c9fd14aa7fdeeb2255eba9c4f99c075ed19b9a.tar.gz
linux-86c9fd14aa7fdeeb2255eba9c4f99c075ed19b9a.tar.bz2
linux-86c9fd14aa7fdeeb2255eba9c4f99c075ed19b9a.zip
gve: trigger RX NAPI instead of TX NAPI in gve_xsk_wakeup
commit fb3a9a1165cea104b5ab3753e88218e4497b01c1 upstream. Commit ba0925c34e0f ("gve: process XSK TX descriptors as part of RX NAPI") moved XSK TX processing to be part of the RX NAPI. However, that commit did not include triggering the RX NAPI in gve_xsk_wakeup. This is necessary because the TX NAPI only processes TX completions, meaning that a TX wakeup would not actually trigger XSK descriptor processing. Also, the branch on XDP_WAKEUP_TX was supposed to have been removed, as the NAPI should be scheduled whether the wakeup is for RX or TX. Fixes: ba0925c34e0f ("gve: process XSK TX descriptors as part of RX NAPI") Cc: stable@vger.kernel.org Signed-off-by: Joshua Washington <joshwash@google.com> Signed-off-by: Praveen Kaligineedi <pkaligineedi@google.com> Link: https://patch.msgid.link/20241221032807.302244-1-pkaligineedi@google.com Signed-off-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions