----- Original Message -----

From: "Xin Zhao" <[email protected]> To: "Hal Finkel" <[email protected]>, [email protected] Cc: "Pavan Balaji" <[email protected]> Sent: Monday, June 30, 2014 2:14:15 PM Subject: RE: MPIR_CVAR_CH3_RMA_GC_NUM_TESTED

Hi Hal,

Currently the RMA operation list is implemented in CH3 layer, whereas the progress engine is implemented in nemesis layer. We didn't pass the list to the nemesis layer but only pass the single request pointer, so the progress engine now only modify on the request pointer.

Thanks for the explanation. FWIW, I don't understand why the calling code (in CH3) could not test for complete upon return from nemesis and handle it then. Which function handles this? -Hal

This is one of the problems we have with the current separation of the CH3 and nemesis layers, we plan to merge these layers in future and this should be fixed at that time.

Thanks, Xin ________________________________________ From: Hal Finkel [[email protected]] Sent: Monday, June 30, 2014 1:28 PM To: [email protected] Cc: Zhao, Xin; Pavan Balaji Subject: Re: MPIR_CVAR_CH3_RMA_GC_NUM_TESTED

Xin, et al.,

Regarding 283319f5d9d1cdbcf016dc0ff8ab284114c0be7e (which added MPIR_CVAR_CH3_RMA_GC_NUM_TESTED and associated code): If a request is completed by the progress engine, why can't the progress engine move it to the beginning of the list (or the end), and have rma_list_gc only search from the beginning (or end) until it finds an incomplete request?

Thanks in advance, Hal

-- Hal Finkel Assistant Computational Scientist Leadership Computing Facility Argonne National Laboratory

-- Hal Finkel Assistant Computational Scientist Leadership Computing Facility Argonne National Laboratory