diff options
author | Maciej Fijalkowski <[email protected]> | 2019-02-13 10:51:06 -0800 |
---|---|---|
committer | Jeff Kirsher <[email protected]> | 2019-03-25 09:55:35 -0700 |
commit | 712edbbb67d404bae055d88e162e13980b426663 (patch) | |
tree | 5397503461d62c9ba567b37a5ba2e9a0dc26c7cf /tools/perf/scripts/python/export-to-sqlite.py | |
parent | 1d032bc77bb8f85d8adfd14a1a8c67c12b07eece (diff) |
ice: Limit the ice_add_rx_frag to frag addition
Refactor ice_fetch_rx_buf and ice_add_rx_frag in a way that we have
standalone functions that do either the skb construction or frag
addition to previously constructed skb.
The skb handling between rx_bufs is spread among various functions. The
ice_get_rx_buf will retrieve the skb pointer from rx_buf and if it is a
NULL pointer then we do the ice_construct_skb, otherwise we add a frag
to the current skb via ice_add_rx_frag. Then, on the ice_put_rx_buf the
skb pointer that belongs to rx_buf will be cleared. Moving further, if
the current frame is not EOP frame we assign the current skb to the
rx_buf that is pointed by updated next_to_clean indicator.
What is more during the buffer reuse let's assign each member of
ice_rx_buf individually so we avoid the unnecessary copy of skb.
Last but not least, this logic split will allow us for better code reuse
when adding a support for build_skb.
Signed-off-by: Maciej Fijalkowski <[email protected]>
Signed-off-by: Anirudh Venkataramanan <[email protected]>
Tested-by: Andrew Bowers <[email protected]>
Signed-off-by: Jeff Kirsher <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions