| commit | 990c3d6f9c4115347659fc2b163907c8c832ae44 | |
| author | Neil Horman <nhorman@tuxdriver.com> | |
| Wed, 13 Oct 2010 16:01:51 +0000 (13 16:01 +0000) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Mon, 18 Oct 2010 15:32:08 +0000 (18 08:32 -0700) | ||
| tree | d41e68a1c3c34d8439fe886b96c18fec4d954604 | treesnapshot (tar.gz zip) |
| parent | e843fa50887582c867d8b7995f81fe9c1a076806 | commitdiff |
bonding: Fix napi poll for bonding driver
Usually the netpoll path, when preforming a napi poll can get away with just
polling all the napi instances of the configured device. Thats not the case for
the bonding driver however, as the napi instances which may wind up getting
flagged as needing polling after the poll_controller call don't belong to the
bonded device, but rather to the slave devices. Fix this by checking the device
in question for the IFF_MASTER flag, if set, we know we need to check the full
poll list for this cpu, rather than just the devices napi instance list.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Usually the netpoll path, when preforming a napi poll can get away with just
polling all the napi instances of the configured device. Thats not the case for
the bonding driver however, as the napi instances which may wind up getting
flagged as needing polling after the poll_controller call don't belong to the
bonded device, but rather to the slave devices. Fix this by checking the device
in question for the IFF_MASTER flag, if set, we know we need to check the full
poll list for this cpu, rather than just the devices napi instance list.
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
| net/core/netpoll.c | diffblobblamehistory |