[ofw] [PATCH 07/12] dapl-2.0: common: dat_ep_connect should not set timer UD endpoints

Davis, Arlin R arlin.r.davis at intel.com
Wed May 19 11:11:31 PDT 2010


connect for UD type is simply AH resolution and doesn't
need timed. The common code is not designed to handle
multiple timed events on connect requests so just ignore
timing UD AH requests.

Signed-off-by: Arlin Davis <arlin.r.davis at intel.com>
---
 dapl/common/dapl_ep_connect.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/dapl/common/dapl_ep_connect.c b/dapl/common/dapl_ep_connect.c
index 1f193ae..9b5829e 100755
--- a/dapl/common/dapl_ep_connect.c
+++ b/dapl/common/dapl_ep_connect.c
@@ -327,7 +327,8 @@ dapl_ep_connect(IN DAT_EP_HANDLE ep_handle,
 		dapl_os_lock(&ep_ptr->header.lock);
 		if (ep_ptr->param.ep_state ==
 		    DAT_EP_STATE_ACTIVE_CONNECTION_PENDING
-		    && timeout != DAT_TIMEOUT_INFINITE) {
+		    && timeout != DAT_TIMEOUT_INFINITE &&
+	    	    ep_ptr->param.ep_attr.service_type == DAT_SERVICE_TYPE_RC) {
 			ep_ptr->cxn_timer =
 			    (DAPL_OS_TIMER *)
 			    dapl_os_alloc(sizeof(DAPL_OS_TIMER));
-- 
1.5.2.5




More information about the ofw mailing list