Sean Hefty 82a9c16a10 IB/cm: Send DREP in response to unmatched DREQ ... Currently a DREP is only sent in response to a DREQ if a connection has been found matching the DREQ, and it is in the proper state. Once a DREP is sent, the local connection moves into timewait. Duplicate DREQs received while in this state result in re-sending the DREP. However, it's likely that the local connection will enter and exit timewait before the remote side times out a lost DREP and resends a DREQ. To handle this, we send a DREP in response to a DREQ, even if a local connection is not found. This avoids maintaining disconnected id's in timewait states for excessively long times, just to handle a lost DREP. Signed-off-by: Sean Hefty <sean.hefty@intel.com> Signed-off-by: Roland Dreier <rolandd@cisco.com>		2006-10-10 12:50:38 -07:00
..
addr.c
agent.c
agent.h
cache.c
cm_msgs.h
cm.c	IB/cm: Send DREP in response to unmatched DREQ	2006-10-10 12:50:38 -07:00
cma.c
core_priv.h
device.c
fmr_pool.c
iwcm.c
iwcm.h
mad_priv.h
mad_rmpp.c
mad_rmpp.h
mad.c
Makefile
packer.c
sa_query.c
smi.c
smi.h
sysfs.c
ucm.c
ud_header.c
user_mad.c
uverbs_cmd.c
uverbs_main.c
uverbs_marshall.c
uverbs_mem.c
uverbs.h
verbs.c