summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorBjörn Töpel <bjorn.topel@intel.com>2020-12-11 17:57:12 +0300
committerJakub Kicinski <kuba@kernel.org>2020-12-16 21:51:07 +0300
commit64050b5b8706d304ba647591b06e1eddc55e8bd9 (patch)
tree371bc1fdaaeb6fe6b187afc334ac954221551a38 /tools/perf/scripts/python/export-to-postgresql.py
parent8d14768a7972b92c73259f0c9c45b969d85e3a60 (diff)
downloadlinux-64050b5b8706d304ba647591b06e1eddc55e8bd9.tar.xz
i40e, xsk: clear the status bits for the next_to_use descriptor
On the Rx side, the next_to_use index points to the next item in the HW ring to be refilled/allocated, and next_to_clean points to the next item to potentially be processed. When the HW Rx ring is fully refilled, i.e. no packets has been processed, the next_to_use will be next_to_clean - 1. When the ring is fully processed next_to_clean will be equal to next_to_use. The latter case is where a bug is triggered. If the next_to_use bits are not cleared, and the "fully processed" state is entered, a stale descriptor can be processed. The skb-path correctly clear the status bit for the next_to_use descriptor, but the AF_XDP zero-copy path did not do that. This change adds the status bits clearing of the next_to_use descriptor. Fixes: 3b4f0b66c2b3 ("i40e, xsk: Migrate to new MEM_TYPE_XSK_BUFF_POOL") Signed-off-by: Björn Töpel <bjorn.topel@intel.com> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions