Moni Shoua f0f6f346a1 IB/mlx4: Fix dispatch of IB_EVENT_LID_CHANGE event ... When snooping a PortInfo MAD, its client_reregister bit is checked. If the bit is ON then a CLIENT_REREGISTER event is dispatched, otherwise a LID_CHANGE event is dispatched. This way of decision ignores the cases where the MAD changes the LID along with an instruction to reregister (so a necessary LID_CHANGE event won't be dispatched) or the MAD is neither of these (and an unnecessary LID_CHANGE event will be dispatched). This causes problems at least with IPoIB, which will do a "light" flush on reregister, rather than the "heavy" flush required due to a LID change. Fix this by dispatching a CLIENT_REREGISTER event if the client_reregister bit is set, but also compare the LID in the MAD to the current LID. If and only if they are not identical then a LID_CHANGE event is dispatched. Signed-off-by: Moni Shoua <monis@voltaire.com> Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il> Signed-off-by: Yossi Etigin <yosefe@voltaire.com> Signed-off-by: Roland Dreier <rolandd@cisco.com>		2009-01-28 14:54:35 -08:00
..
core	infiniband: struct device - replace bus_id with dev_name(), dev_set_name()	2009-01-06 10:44:39 -08:00
hw	IB/mlx4: Fix dispatch of IB_EVENT_LID_CHANGE event	2009-01-28 14:54:35 -08:00
ulp	IPoIB: Do not print error messages for multicast join retries	2009-01-16 13:42:59 -08:00
Kconfig	RDMA/addr: Fix build breakage when IPv6 is disabled	2008-12-29 23:37:14 -08:00
Makefile