bnx2x: Correct ringparam estimate when DOWN
authorMintz, Yuval <Yuval.Mintz@cavium.com>
Sun, 4 Dec 2016 13:30:17 +0000 (15:30 +0200)
committerDavid S. Miller <davem@davemloft.net>
Mon, 5 Dec 2016 20:08:39 +0000 (15:08 -0500)
commit65870fa77fd7f83d7be4ed924d47ed9e3831f434
treeb9590fba709353e6a68cc3f31ba07d24737c25cd
parent9a53682b340b97642793271ba095cc9531a7b649
bnx2x: Correct ringparam estimate when DOWN

Until interface is up [and assuming ringparams weren't explicitly
configured] when queried for the size of its rings bnx2x would
claim they're the maximal size by default.
That is incorrect as by default the maximal number of buffers would
be equally divided between the various rx rings.

This prevents the user from actually setting the number of elements
on each rx ring to be of maximal size prior to transitioning the
interface into up state.

To fix this, make a rough estimation about the number of buffers.
It wouldn't always be accurate, but it would be much better than
current estimation and would allow users to increase number of
buffers during early initialization of the interface.

Reported-by: Seymour, Shane <shane.seymour@hpe.com>
Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/net/ethernet/broadcom/bnx2x/bnx2x_ethtool.c