diff options
author | David Wei <dw@davidwei.uk> | 2024-12-03 20:10:22 -0800 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2024-12-04 19:23:35 -0800 |
commit | bd649c5cc958169b8a8a3e77ea926d92d472b02a (patch) | |
tree | 593fb627db19cd290234b1e8d63b78926ce3953e /drivers/net/ethernet/intel/ice/ice_main.c | |
parent | bf1782d70ddd9f23911824e41df8d9b5244f2f30 (diff) | |
download | linux-bd649c5cc958169b8a8a3e77ea926d92d472b02a.tar.gz linux-bd649c5cc958169b8a8a3e77ea926d92d472b02a.tar.bz2 linux-bd649c5cc958169b8a8a3e77ea926d92d472b02a.zip |
bnxt_en: handle tpa_info in queue API implementation
Commit 7ed816be35ab ("eth: bnxt: use page pool for head frags") added a
page pool for header frags, which may be distinct from the existing pool
for the aggregation ring. Prior to this change, frags used in the TPA
ring rx_tpa were allocated from system memory e.g. napi_alloc_frag()
meaning their lifetimes were not associated with a page pool. They can
be returned at any time and so the queue API did not alloc or free
rx_tpa.
But now frags come from a separate head_pool which may be different to
page_pool. Without allocating and freeing rx_tpa, frags allocated from
the old head_pool may be returned to a different new head_pool which
causes a mismatch between the pp hold/release count.
Fix this problem by properly freeing and allocating rx_tpa in the queue
API implementation.
Signed-off-by: David Wei <dw@davidwei.uk>
Reviewed-by: Michael Chan <michael.chan@broadcom.com>
Link: https://patch.msgid.link/20241204041022.56512-4-dw@davidwei.uk
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net/ethernet/intel/ice/ice_main.c')
0 files changed, 0 insertions, 0 deletions