Version: 1
-Previous: 6eda70e1ca5154dc1a32cf8351fc9c69f434d0a1
-Head: 203f6240e2d31e82f784623a8b5a514fdf2f1f7c
+Previous: e2683538fc54f47a129e5e3109304d895595b8f2
+Head: cbeac59b641ada456b6f329bf1df0c24f2f6ac46
Applied:
dapl-update: 2df1438b75e945d48a63fbda74079a77978f315d
cma-priv-data: 83299e9a772068a302a4d39ff4e7ba45d4bd26b5
ibal-disc: 203f6240e2d31e82f784623a8b5a514fdf2f1f7c
+ ibal-drep: cbeac59b641ada456b6f329bf1df0c24f2f6ac46
Unapplied:
dapl-cookie: dba881d08766e12ba2863c4f57b6a1877b5a8ecf
dapl-evd: ede541a6ba3d7d2a69f95b691f69eb9a315bb75d
--- /dev/null
+Bottom: f7f2d544218a134f3c4d7ef793f728f1ee392dbf
+Top: f7f2d544218a134f3c4d7ef793f728f1ee392dbf
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2010-09-23 12:25:29 -0700
+
+ibal: send drep in response to unmatched dreq
+
+If a DREQ is received that cannot be matched with an
+existing CEP, issue a DREP in response. It's possible
+that the targetted CEP issued a DREP which was lost.
+The CEP then transitioned through the timewait state
+before another DREQ was received, and is no longer accessible.
+To prevent the remote side from timing out waiting on a DREP,
+send one so that it can complete its disconnection.
+
+This fixes an issue in iMPI where one side of a connection
+ends up waiting up to two minutes on disconnection.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+