Ben Greear <gree...@candelatech.com> wrote:
The blacklist option worked.I blacklisted both ixgbe and igb, and then added a pre_network init.d script that runs before the 'network' target. This script loads ixgbe, waits 2 seconds, loads igb.I now see all network devices registered. This is quite a bit of a hack though, so I plan to still try a module param to limit number of txqueues for igb and ixgbe.
I really doubt that such a patch will be accepted, because there is an ethtool option for controlling the number of "channels" for a network device. That won't work in your case, because the driver fails to initialize before you can reduce the number of queues used by other devices. But I can see that the parameter would be useful for what you are doing.
Probably will be a bit before I get to that though....
I'm glad that something worked. Enabling the high decoding was a good thing to do even though it didn't resolve this issue.
-- Mark Rustad, Networking Division, Intel Corporation
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi
_______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
