Ben Greear <gree...@candelatech.com> wrote:
Thanks for the diagnosis.The purpose of this system is to act as a network traffic generation test system, and we do not expect full line-rate throughput on all ports concurrently. We do see nice throughput over-all on this sytem (in previous boots we tested all NICs concurrently, probably we got lucky andixgbe loaded first perhaps?)We can test this blacklist option, but is there also a way to tell igb to just not grab so many MSI-X interrupts? In my particular use case, I don't think they will add a lot of benefit.
Well, all of these drivers try to get ncpus + 1 interrupts. So you could reduce the number of cpus via a command line option. That is, if you would still have enough cpu. Or turn off hyperthreading if it is on. Or modify the igb driver to limit the number of queues. There are no module parameters for such things, because module parameters are rarely accepted upstream, so we don't put effort into them.
-- 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
