ice: introduce frame padding computation logic

Browse source

Take into account the underlying architecture specific settings and
based on that calculate the possible padding that can be supplied.
Typically, for x86 and standard MTU size we will end up with 192 bytes
of headroom. This is the same behavior as our other drivers have and we
can dedicate it for XDP purposes.

Furthermore, introduce the Rx ring flag for indicating whether build_skb
is used on particular. Based on that invoke the routines for padding
calculation.

Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

...

This commit is contained in:

Maciej Fijalkowski 2019-10-24 01:11:23 -07:00 • committed by Jeff Kirsher

parent 7237f5b0db

commit 59bb080805

5 changed files with 114 additions and 20 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

6

drivers/net/ethernet/intel/ice/ice_base.c

View file

2

drivers/net/ethernet/intel/ice/ice_ethtool.c

View file

3

drivers/net/ethernet/intel/ice/ice_lib.c

View file

42

drivers/net/ethernet/intel/ice/ice_txrx.c

View file

81

drivers/net/ethernet/intel/ice/ice_txrx.h

View file