From 1cfd739e8f3cdf3c4f522f2203f9e28d55f937ee Mon Sep 17 00:00:00 2001 From: mubarak Date: Thu, 28 Sep 2017 15:24:09 -0500 Subject: [PATCH] Fixing irecv next event issue --- src/network-workloads/model-net-mpi-replay.c | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/src/network-workloads/model-net-mpi-replay.c b/src/network-workloads/model-net-mpi-replay.c index 0e9ba65..f1e6f3e 100644 --- a/src/network-workloads/model-net-mpi-replay.c +++ b/src/network-workloads/model-net-mpi-replay.c @@ -1320,19 +1320,18 @@ static void codes_exec_mpi_recv( int found_matching_sends = rm_matching_send(s, bf, m, lp, recv_op); + /* for mpi irecvs, this is a non-blocking receive so just post it and move on with the trace read. */ + if(mpi_op->op_type == CODES_WK_IRECV) + { + bf->c6 = 1; + codes_issue_next_event(lp); + } /* save the req id inserted in the completed queue for reverse computation. */ if(found_matching_sends < 0) { m->fwd.found_match = -1; qlist_add(&recv_op->ql, &s->pending_recvs_queue); - /* for mpi irecvs, this is a non-blocking receive so just post it and move on with the trace read. */ - if(mpi_op->op_type == CODES_WK_IRECV) - { - bf->c6 = 1; - codes_issue_next_event(lp); - return; - } } else { -- 2.26.2