usnic: gracefully handle when we can't alloc an ACK

jsquyres · jsquyres · commit 633da6641e5a · 2015-07-10T14:19:33.000-07:00
The comment didn't match the debugging code (which was ugly, and
apparently never happens, anyway).  Just return and let the sender
retransmit.
diff --git a/opal/mca/btl/usnic/btl_usnic_ack.c b/opal/mca/btl/usnic/btl_usnic_ack.c
@@ -201,8 +201,7 @@ opal_btl_usnic_ack_send(
     /* Get an ACK frag.  If we don't get one, just discard this ACK. */
     ack = opal_btl_usnic_ack_segment_alloc(module);
     if (OPAL_UNLIKELY(NULL == ack)) {
-        opal_output(0, "====================== No frag for sending the ACK -- skipped");
-        abort();
+        return;
     }
 
     /* send the seq of the lowest item in the window that

Original file line number	Diff line number	Diff line change
`@@ -201,8 +201,7 @@ opal_btl_usnic_ack_send(`
`201`	`201`	`/* Get an ACK frag. If we don't get one, just discard this ACK. */`
`202`	`202`	`ack = opal_btl_usnic_ack_segment_alloc(module);`
`203`	`203`	`if (OPAL_UNLIKELY(NULL == ack)) {`
`204`		`- opal_output(0, "====================== No frag for sending the ACK -- skipped");`
`205`		`- abort();`
	`204`	`+ return;`
`206`	`205`	`}`
`207`	`206`
`208`	`207`	`/* send the seq of the lowest item in the window that`