idpf: use libeth Rx buffer management for payload buffer

Browse source

idpf uses Page Pool for data buffers with hardcoded buffer lengths of
4k for "classic" buffers and 2k for "short" ones. This is not flexible
and does not ensure optimal memory usage. Why would you need 4k buffers
when the MTU is 1500?
Use libeth for the data buffers and don't hardcode any buffer sizes. Let
them be calculated from the MTU for "classics" and then divide the
truesize by 2 for "short" ones. The memory usage is now greatly reduced
and 2 buffer queues starts make sense: on frames <= 1024, you'll recycle
(and resync) a page only after 4 HW writes rather than two.

Signed-off-by: Alexander Lobakin <aleksander.lobakin@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

...

This commit is contained in:

Alexander Lobakin 2024-06-20 15:53:47 +02:00 • committed by Tony Nguyen

parent 90912f9f4f

commit 74d1412ac8

6 changed files with 120 additions and 246 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

1

drivers/net/ethernet/intel/idpf/Kconfig

View file

2

drivers/net/ethernet/intel/idpf/idpf.h

View file

27

drivers/net/ethernet/intel/idpf/idpf_singleq_txrx.c

View file

242

drivers/net/ethernet/intel/idpf/idpf_txrx.c

View file

86

drivers/net/ethernet/intel/idpf/idpf_txrx.h

View file

8

drivers/net/ethernet/intel/idpf/idpf_virtchnl.c

View file