diff options
| author | Michal Schmidt <mschmidt@redhat.com> | 2015-04-27 17:20:38 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2015-04-27 13:42:39 -0400 |
| commit | 22a8f237c0551bae95ffcd2a7ff17d6f5fcce7e7 (patch) | |
| tree | dcf7a9c4c678f20cbaa3d5201b8ae668eac10d6e /Documentation | |
| parent | 94435f764cc5838a7e94008f17628ad63384bf06 (diff) | |
| download | linux-rpi-22a8f237c0551bae95ffcd2a7ff17d6f5fcce7e7.tar.gz linux-rpi-22a8f237c0551bae95ffcd2a7ff17d6f5fcce7e7.tar.bz2 linux-rpi-22a8f237c0551bae95ffcd2a7ff17d6f5fcce7e7.zip | |
bnx2x: really disable TPA if 'disable_tpa' option is set
bnx2x's 'disable_tpa=1' module option is not respected properly and TPA
(transparent packet aggregation) remains enabled. Even though the
module option causes LRO to be disabled, TPA is enabled in GRO mode.
Additionally, disabling GRO via ethtool then has no effect. One can
still observe tpa_* statistics increase and large packets being received
in tcpdump.
The bug was an unintended consequence of commit aebf6244cd39 "bnx2x: Be
more forgiving toward SW GRO".
Fix it by following the bp->disable_tpa flag when initializing fp's.
Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions