bnxt_en: remove DMA mapping for KONG response

Browse source

The additional response buffer serves no useful purpose. There can
be only one firmware command in flight due to the hwrm_cmd_lock mutex,
which is taken for the entire duration of any command completion,
KONG or otherwise. It is thus safe to share a single DMA buffer.

Removing the code associated with the additional mapping will simplify
matters in the next patch, which allocates response buffers from DMA
pools on a per request basis.

Signed-off-by: Edwin Peer <edwin.peer@broadcom.com>
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

...

This commit is contained in:

Edwin Peer 2021-08-29 03:34:56 -04:00 • committed by David S. Miller

parent eaf2aaec0b

commit 6c172d59ad

2 changed files with 7 additions and 51 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

42

drivers/net/ethernet/broadcom/bnxt/bnxt.c

View file

16

drivers/net/ethernet/broadcom/bnxt/bnxt.h

View file