igb: Add support for ethtool private flag to allow use of legacy Rx
authorAlexander Duyck <alexander.h.duyck@intel.com>
Tue, 7 Feb 2017 02:26:52 +0000 (18:26 -0800)
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>
Fri, 17 Mar 2017 19:11:44 +0000 (12:11 -0700)
commite08912985b296b33b18a563cc126e3e2f018c2e1
treebcda6f91c74765d410c0f331110cbed53dfe77ab
parent3456fd53421e7f499395542d6c2e76e0b46ab4d3
igb: Add support for ethtool private flag to allow use of legacy Rx

Since there are potential drawbacks to the new Rx allocation approach I
thought it best to add a "chicken bit" so that we can turn the feature off
if in the event that a problem is found.

It also provides a means of validating the legacy Rx path in the event that
we are forced to fall back.  At some point in the future when we are
convinced we don't need it anymore we might be able to drop the legacy-rx
flag.

Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
drivers/net/ethernet/intel/igb/igb.h
drivers/net/ethernet/intel/igb/igb_ethtool.c