*** This bug has been split off bug 140790 ***
Description of problem:
Currently, ethtool calls to e100 or e1000 to set rx-mini or rx-jumbo appear to
succeed although nothing is actually done. This behavior can be misconstrued as
successful setting of the parameter(s). The drivers should be either add support
for setting these values or return EINVAL.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run 'ethtool -G eth1 rx-mini 64' or 'ethtool -G eth1 rx-jumbo 64' on an e100
2. check adapter's settings to verify the change was not made ('ethtool -g eth1')
Nothing was changed as the rx-mini and rx-jumbo settings are ignored by the
drivers' ethtool handlers.
Either adjust the settings as requested or issue an error indicating lack of
support for the adjustment of given parameter.
FYI as of release 7.0.33 of the intel drivers this was merged. 7.0.33 arrived
upstream in 2.6.17-rc1.
git commit 0989aa431636ffb347314f0e2f367fdd16d7a57f
# ethtool -i eth1
# ethtool -G eth1 rx-jumbo 128
Cannot set device ring parameters: Invalid argument
seems confirmed to me