diff options
author | Leonid Arsh <leonida@voltaire.com> | 2006-03-23 19:52:51 +0200 |
---|---|---|
committer | Roland Dreier <rolandd@cisco.com> | 2006-03-24 15:47:30 -0800 |
commit | 7a343d4c46bc59fe617f968e996ce2fd67c5d179 (patch) | |
tree | bc58caefafd0e1228266a0928f5d70aa5f262cf4 /drivers/cpufreq/Makefile | |
parent | 192daa18dd7bfcaeb092a2ef928135745f2e6883 (diff) |
IPoIB: P_Key change event handling
This patch causes the network interface to respond to P_Key change
events correctly. As a result, you'll see a child interface in the
"RUNNING" state (netif_carrier_on()) only when the corresponding P_Key
is configured by the SM. When SM removes a P_Key, the "RUNNING" state
will be disabled for the corresponding network interface. To
implement this, I added IB_EVENT_PKEY_CHANGE event handling. To
prevent flushing the device before the device is open by the "delay
open" mechanism, I added an additional device flag called
IPOIB_FLAG_INITIALIZED.
This also prevents the child network interface from trying to join to
multicast groups until the PKEY is configured. We used to get error
messages like:
ib0.f2f2: couldn't attach QP to multicast group ff12:401b:f2f2:0:0:0:ffff:ffff
in this case. To fix this, I just check IPOIB_FLAG_OPER_UP flag in
ipoib_set_mcast_list().
Signed-off-by: Leonid Arsh <leonida@voltaire.com>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
Diffstat (limited to 'drivers/cpufreq/Makefile')
0 files changed, 0 insertions, 0 deletions