summaryrefslogtreecommitdiff
path: root/drivers/net/fjes/fjes_main.c
diff options
context:
space:
mode:
authorJon Maxwell <jmaxwell37@gmail.com>2016-01-25 10:22:52 +1100
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2016-02-24 15:45:50 -0800
commitcc54a59ae6e528c70666033ed085d059f555a57d (patch)
tree7d1390008f4f7069bd4d475a7bac69baef2302b4 /drivers/net/fjes/fjes_main.c
parentea6ce6024f9397ff2667fe16447447e622bc4c31 (diff)
igbvf: remove "link is Up" message when registering mcast address
A similar issue was addressed a few years ago in the following thread: http://www.spinics.net/lists/netdev/msg245877.html At that time there were concerns that removing this statement may cause other side effects. However the submitter addressed those concerns. But the dialogue went cold. We have a new case where a customers application is registering and un-registering multicast addresses every few seconds. This is leading to many "Link is Up" messages in the logs as a result of the "netif_carrier_off(netdev)" statement called by igbvf_msix_other(). Also on some kernels it is interfering with the bonding driver causing it to failover and subsequently affecting connectivity. The Sourgeforge driver does not make this call and is therefore not affected. If there were any side effects I would expect that driver to also be affected. I have tested re-loading the igbvf driver and downing the adapter with the PF entity on the host where the VM has this patch. When I bring it back up again connectivity is restored as expected. Therefore I request that this patch gets submitted. Signed-off-by: Jon Maxwell <jmaxwell37@gmail.com> Tested-by: Aaron Brown <aaron.f.brown@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'drivers/net/fjes/fjes_main.c')
0 files changed, 0 insertions, 0 deletions