Searched hist:"89861 c485c6a384e298fb78660d6a773339e42b1" (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/drivers/net/ethernet/intel/ice/ |
H A D | ice_base.c | diff 89861c485c6a384e298fb78660d6a773339e42b1 Wed Mar 03 09:39:27 CST 2021 Maciej Fijalkowski <maciej.fijalkowski@intel.com> ice: move headroom initialization to ice_setup_rx_ctx
ice_rx_offset(), that is supposed to initialize the Rx buffer headroom, relies on ICE_RX_FLAGS_RING_BUILD_SKB flag as well as XDP prog presence.
Currently, the callsite of mentioned function is placed incorrectly within ice_setup_rx_ring() where Rx ring's build skb flag is not set yet. This causes the XDP_REDIRECT to be partially broken due to inability to create xdp_frame in the headroom space, as the headroom is 0.
Fix this by moving ice_rx_offset() to ice_setup_rx_ctx() after the flag setting.
Fixes: f1b1f409bf79 ("ice: store the result of ice_rx_offset() onto ice_ring") Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com> Tested-by: Kiran Bhandare <kiranx.bhandare@intel.com> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
|
H A D | ice_txrx.c | diff 89861c485c6a384e298fb78660d6a773339e42b1 Wed Mar 03 09:39:27 CST 2021 Maciej Fijalkowski <maciej.fijalkowski@intel.com> ice: move headroom initialization to ice_setup_rx_ctx
ice_rx_offset(), that is supposed to initialize the Rx buffer headroom, relies on ICE_RX_FLAGS_RING_BUILD_SKB flag as well as XDP prog presence.
Currently, the callsite of mentioned function is placed incorrectly within ice_setup_rx_ring() where Rx ring's build skb flag is not set yet. This causes the XDP_REDIRECT to be partially broken due to inability to create xdp_frame in the headroom space, as the headroom is 0.
Fix this by moving ice_rx_offset() to ice_setup_rx_ctx() after the flag setting.
Fixes: f1b1f409bf79 ("ice: store the result of ice_rx_offset() onto ice_ring") Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com> Tested-by: Kiran Bhandare <kiranx.bhandare@intel.com> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
|