1
1

Ensure we know how to route to a different job family when it connects to us

This commit was SVN r19885.
Этот коммит содержится в:
Ralph Castain 2008-11-03 14:25:14 +00:00
родитель 85bc7bb26a
Коммит 55f52d7a4b

Просмотреть файл

@ -480,13 +480,6 @@ static void mca_oob_tcp_msg_data(mca_oob_tcp_msg_t* msg, mca_oob_tcp_peer_t* pee
* not know how to route any reply back to the originator. Update
* our route so we can dynamically build the routing table
*/
/* if the origin and the src are the same, then we don't need to do
* this - update_route was already called when the connection was
* established in oob_tcp_peer
*/
if (OPAL_EQUAL != orte_util_compare_name_fields(ORTE_NS_CMP_ALL,
&(msg->msg_hdr.msg_origin),
&(msg->msg_hdr.msg_src))) {
if (ORTE_SUCCESS != (rc = orte_routed.update_route(&(msg->msg_hdr.msg_origin),
&(msg->msg_hdr.msg_src)))) {
/* Nothing we can do about errors here as we definitely want
@ -495,7 +488,6 @@ static void mca_oob_tcp_msg_data(mca_oob_tcp_msg_t* msg, mca_oob_tcp_peer_t* pee
ORTE_ERROR_LOG(rc);
}
}
}
/* match msg against posted receives */
post = mca_oob_tcp_msg_match_post(&msg->msg_hdr.msg_origin, msg->msg_hdr.msg_tag);